Systems and methods for post-quantum cryptography communications channels

ABSTRACT

Systems, apparatuses, methods, and computer program products are disclosed for PQC. An example method includes transmitting a first portion of an electronic communication to a client device over a non-PQC communications channel. The example method further includes transmitting a second portion of the electronic communication to a PQC add-on device over a PQC communications channel, wherein the PQC add-on device is communicatively coupled to the client device. In some instances, the first portion of the electronic communication may comprise overhead data, and the second portion of the electronic communication may comprise payload data.

TECHNOLOGICAL FIELD

Example embodiments of the present disclosure relate generally tocryptography and, more particularly, to systems and methods forproviding post-quantum cryptography (PQC).

BACKGROUND

Although still in its infancy, quantum computing and its boundlesspotential applications are of rapidly increasing interest to a broadarray of industrial sectors, including simulation, artificialintelligence, healthcare, and financial services. Unlike classicalcomputers, which process information in bits that can only represent oneof two binary information states at a time, quantum computers processinformation in quantum bits (qubits) that can represent a coherentsuperposition of both binary information states at the same time.Further, two or more qubits may be entangled so that their physicalproperties are correlated even when separated by large distances, andquantum computers may simultaneously perform a vast number of operationson these entangled qubits. This massive parallelism allows quantumcomputers to perform incredibly complex calculations at speedsunimaginable today and solve certain classes of problems that are beyondthe capability of today's most powerful supercomputers.

Reflecting this broad potential impact, companies from a variety ofmarket sectors are investing substantial resources to develop thesepromising quantum computing theories into real-world quantum computingcapabilities. However, this heightened interest and investment has yetto produce an enduring and functional quantum computer outside of alaboratory environment.

Nonetheless, there is widespread agreement among experts that quantumcomputers will disrupt current security protocols that protect globalfinancial markets and governmental institutions. For example, mostcommon public-key cryptography schemes, such as the widely-usedRivest-Shamir-Adleman (RSA) and Diffie-Hellman (DH) schemes, rely on theinability of classical computers to complete certain types of complexmathematical calculations, such as integer factorization and discretelogarithm computation, respectively, within a reasonable amount of time.A quantum computer implementing Shor's algorithm potentially couldcomplete these complex calculations in a relatively short time andthereby determine the private keys used for current public-key systemsfrom the corresponding public keys. Accordingly, there is an urgent needfor data owners and hosting services to begin migrating their data andupgrading their systems to use quantum-resistant algorithms beforequantum computing capabilities are realized. However, the sheer volumeof this data and complexity of these systems presents myriad challengesto any such migration plan.

BRIEF SUMMARY

Computing systems, computing apparatuses, computer-implemented methods,and computer program products are disclosed herein for improvedpost-quantum cryptography (PQC) for migrating classical informationsystems to quantum-resistant systems using one or more of the PQCcryptographic techniques described herein. In some embodiments, the PQCsystem provided herein solves the above problems by transmitting a firstportion of an electronic communication (e.g., message overhead data) toa client device over a non-PQC communications channel and transmitting asecond portion of the electronic communication (e.g., message payloaddata) to a PQC add-on device over a PQC communications channel, whereinthe PQC add-on device is communicatively coupled to the client device.

In one example embodiment, a system is provided for PQC. The system maycomprise classical communications circuitry configured to transmit afirst portion of an electronic communication to a client device over anon-PQC communications channel. The system may further comprise PQCcallback circuitry configured to transmit a second portion of theelectronic communication to a PQC add-on device over a PQCcommunications channel, wherein the PQC add-on device is communicativelycoupled to the client device. In some embodiments, the first portion ofthe electronic communication may comprise overhead data, and the secondportion of the electronic communication may comprise payload data.

In one example embodiment, an apparatus is provided for PQC. Theapparatus may comprise classical communications circuitry configured totransmit a first portion of an electronic communication to a clientdevice over a non-PQC communications channel. The apparatus may furthercomprise PQC callback circuitry configured to transmit a second portionof the electronic communication to a PQC add-on device over a PQCcommunications channel, wherein the PQC add-on device is communicativelycoupled to the client device. In some embodiments, the first portion ofthe electronic communication may comprise overhead data, and the secondportion of the electronic communication may comprise payload data.

In another example embodiment, a method is provided for PQC. The methodmay comprise transmitting, by classical communications circuitry, afirst portion of an electronic communication to a client device over anon-PQC communications channel. The method may further comprisetransmitting, by PQC callback circuitry, a second portion of theelectronic communication to a PQC add-on device over a PQCcommunications channel, wherein the PQC add-on device is communicativelycoupled to the client device. In some embodiments, the first portion ofthe electronic communication may comprise overhead data, and the secondportion of the electronic communication may comprise payload data.

In another example embodiment, a computer program product is providedfor PQC. The computer program product comprises at least onenon-transitory computer-readable storage medium storing programinstructions that, when executed, may cause a system to transmit a firstportion of an electronic communication to a client device over a non-PQCcommunications channel. The program instructions, when executed, mayfurther cause the system to transmit a second portion of the electroniccommunication to a PQC add-on device over a PQC communications channel,wherein the PQC add-on device is communicatively coupled to the clientdevice. In some embodiments, the first portion of the electroniccommunication may comprise overhead data, and the second portion of theelectronic communication may comprise payload data.

The foregoing brief summary is provided merely for purposes ofsummarizing some example embodiments illustrating some aspects of thepresent disclosure. Accordingly, it will be appreciated that theabove-described embodiments are merely examples and should not beconstrued to narrow the scope of the present disclosure in any way. Itwill be appreciated that the scope of the present disclosure encompassesmany potential embodiments in addition to those summarized herein, someof which will be described in further detail below.

BRIEF DESCRIPTION OF THE FIGURES

The accompanying figures, which are not necessarily drawn to scale,illustrate embodiments and features of the present disclosure. Togetherwith the specification, including the brief summary above and thedetailed description below, the accompanying figures serve to explainthe embodiments and features of the present disclosure. The componentsillustrated in the figures represent components that may or may not bepresent in various embodiments or features of the disclosure describedherein. Accordingly, some embodiments or features of the presentdisclosure may include fewer or more components than those shown in thefigures while not departing from the scope of the disclosure.

FIG. 1 illustrates a system diagram of a set of devices that may beinvolved in some example embodiments described herein;

FIGS. 2A, 2B, and 2C illustrate schematic block diagrams of examplecircuitries that may perform various operations in accordance with someexample embodiments described herein;

FIGS. 3A and 3B illustrate example PQC system architectures configuredto perform various operations in accordance with some exampleembodiments described herein;

FIGS. 4A and 4B illustrate example PQC system architectures configuredto perform various operations in accordance with some exampleembodiments described herein;

FIG. 5 illustrates an example PQC system architecture configured toperform various operations in accordance with some example embodimentsdescribed herein;

FIGS. 6A and 6B illustrate example flowcharts for transmitting andreceiving data over a PQC communications channel in accordance with someexample embodiments described herein;

FIGS. 7A, 7B, and 7C illustrate example flowcharts for transmitting andreceiving data over a PQC communications channel using a PQC add-ondevice in accordance with some example embodiments described herein; and

FIGS. 8A and 8B illustrate example flowcharts for authenticating asession over a quantum communications channel and subsequentlytransmitting and receiving data over a PQC communications channel inaccordance with some example embodiments described herein.

DETAILED DESCRIPTION

Some embodiments of the present disclosure will now be described morefully hereinafter with reference to the accompanying figures, in whichsome, but not all embodiments of the disclosures are shown. Indeed,these disclosures may be embodied in many different forms and should notbe construed as limited to the embodiments set forth herein; rather,these embodiments are provided so that this disclosure will satisfyapplicable legal requirements. Like numbers refer to like elementsthroughout.

Overview

As noted above, methods, apparatuses, systems, and computer programproducts are described herein that provide for migrating classicalinformation systems to quantum-resistant information systems using oneor more of the PQC cryptographic techniques described herein.Traditionally, data owners and third-party hosting services use hybridcryptosystems to safeguard the confidentiality, integrity, andauthenticity of enormous volumes of protected data and complex ITsystems. These hybrid cryptosystems typically use a combination ofasymmetric cryptography (e.g., public key cryptography), such as theRivest-Shamir-Adleman (RSA) cryptosystem, and symmetric cryptography(e.g., secret key cryptography), such as the Advanced EncryptionStandard (AES). One example of a modern hybrid cryptosystem is theTransport Layer Security (TLS) protocol, which relies on asymmetriccryptography for authentication and key management to establish sessionkeys, and symmetric cryptography for session encryption and integrityvalidation.

However, these cryptosystems are vulnerable to quantum algorithmsimplemented on quantum computers. For instance, asymmetric encryption,key exchange, and digital signature rely on mathematical problems suchas the integer factorization problem (e.g., as used in RSA) and thediscrete logarithm problem (e.g., as used in Digital Signature Algorithm(DSA), Elliptic Curve DSA (ECDSA), Diffie-Hellman (DH), and EllipticCurve DH (ECDH)). It is widely believed that a large-scale faulttolerant quantum computer could effectively break modern public keycryptosystems by solving instances of the integer factorization problemand the discrete logarithm problem quickly enough that keys reverseengineered based on those solutions would still be valid.

In one illustrative example, a quantum computer implementing Shor'salgorithm could determine the private keys used for current public-keysystems in a relatively short time because Shor's algorithm provides afaster cryptanalysis method for solving integer factorization than abrute force method (e.g., guessing prime numbers). For instance, Shor'salgorithm uses the quantum Fourier transform (QFT) instead of its slowerclassical counterpart, the fast Fourier transform (FFT). Further, Shor'salgorithm can be modified to compute discrete logarithms, includingdiscrete logarithms used for elliptic-curve cryptography (ECC).

In another illustrative example, a quantum computer implementingGrover's algorithm could effectively perform an exhaustive key searchbecause Grover's algorithm provides quadratic speedup and thereby couldbrute-force attack an N-bit symmetric cryptographic key in only about2^((N/2)) iterations. In some instances, for symmetric cryptographictechniques that support a doubled key length (e.g., AES supportsdoubling a 128-bit key to 256 bits), doubling the key length of thesymmetric cryptographic key may provide sufficient protection againstGrover's algorithm because a brute-force attack on a 2N-bit symmetriccryptographic key would require about 2^(N) iterations. For example, a256-bit symmetric cryptographic key (e.g., AES-256) may only provide 128bits of security in a quantum computing environment. However, anymigration plan that involves doubling the key length of the symmetriccryptographic key must also evaluate the impact of the doubled keylength on the performance of related applications and the additionalrequirements of computational resources.

Although quantum computers capable of such feats are still believed tobe several years away, the threat of a “harvest now and decrypt laterattack” makes quantum computing an immediate real threat, even if thethreat will not be actionable until a sufficiently robust quantumcomputer is developed in the future. The “harvest now and decrypt laterattack” is a long-game attack where a bad actor scrapes, collects, orharvests (e.g., records and stores) encrypted data, such as datastreaming through the Internet or cloud, by the way of breaches orpassive interception and then hoard the encrypted data, waiting for theday when quantum computers can determine the cryptographic keys to theharvested data. This bad actor could be storing data to or from aspecific website, server, email client, or other target of attack or,given sufficient motivation and resources, recording petabytes of dataeach hour from general internet traffic. Once quantum computers arecapable of determining the cryptographic keys associated with theharvested encrypted data, the bad actor might use those cryptographickeys to decrypt the previously encrypted data. For instance, persistentdata, such as mortgage information and financial records, encrypted ordigitally signed with today's cryptographic algorithms will be at riskeven if the necessary quantum computing technology is not available forseven to ten years or even later. Subsequently, with advancements inartificial intelligence and machine learning and the exponentialincrease in data processing compute power, a bad actor could attack adata vault to extract meaningful information from the decryptedpetabytes of data.

These risks are amplified by the lengthy data retention requirements(e.g., security shelf-life) mandated by government agencies, such as theU.S. Federal Deposit Insurance Corporation (FDIC). Example dataretention requirements for various classes of data records listed in theFDIC's Records Retention Schedule are shown below in Table 1.

TABLE 1 Example data retention requirements for various classes of datarecords listed in the FDIC's Records Retention Schedule. Data RetentionRequirement (also Record Class referred to as “security shelf-life”) TaxInformation 7 years Mortgages 30 Years Auto Loans 6 years Equal CreditOpportunity Act 25 months Truth in Lending Act 2 years Bank Secrecy Act5 years FDIC Activities Permanent Personnel Management (PER4100) 56years Non-Judicial Matters (LAW1330) Close of Matter + 10 years JudicialMatters (LAW1400) Entry of Criminal Restitution + 20 years

Given that data is a highly valuable asset, especially in the financialindustry, there is an urgent need for data owners and hosting servicesto initiate the process of protecting their valuable customerinformation and digital assets even before quantum computingcapabilities are realized. This process primarily involves migratingdata and systems to algorithms that are thought to be quantum-resistant.In an attempt to promulgate quantum-resistant algorithms, the NationalInstitute of Standards and Technology (NIST), a federal agency withinthe U.S. Department of Commerce, has initiated the NIST Post-QuantumCryptography Standardization Process to solicit, evaluate, andstandardize one or more quantum-resistant public-key cryptographicalgorithms. At present, there are many different candidate cryptographicalgorithms believed to be quantum-resistant. However, because thestandardization process is not yet complete, migration of classicalsystems to any one of NIST's candidate cryptographic algorithms couldlater compound the computational and resource burden on data owners andhosting services if NIST does not select that particular cryptographicalgorithm as the standard or makes changes to the proposed cryptographicalgorithms.

Although some quantum-resistant cryptographic algorithms are availabletoday, those algorithms may not be the algorithm, or a variant of thealgorithm, that eventually is approved as part of the NIST Post-QuantumCryptography Standardization Process. Moreover, the adoption of thesealgorithms will, in some instances, be an overly complex andtime-consuming process. First, this migration process is challenging dueto the sheer volume of data consumed by these systems, as well as thegeneral complexity of the systems. For example, financial servicesproviders and their partners each may have data for millions ofcustomers and trillions of transactions stored in various databases. Inaddition, these providers are processing millions of transactions on adaily basis and adding new customer data to their systems. Second, datais stored in more places than ever before and must be encrypted usingdifferent cryptographic keys depending upon whether the data is going tobe protected while in transit, while at rest in-cloud, or while at reston-premises. Governmental regulations, NIST recommendations, andindustry standards and best practices will, in some instances, drive thecryptographic techniques that are used to encrypt the data. Third, manyorganizations use several types of encryption, hashing, and othercryptographic algorithms with varying security architecture depending onthe needs of the data owner or hosting service. Fourth, as shown inTable 1 above, there is the need to protect data for varying durationsto manage legal and regulatory risk, sometimes as long as twenty tothirty years, and even in some cases for over fifty years. Fifth, thedeployment of fundamental changes to infrastructure might take a decadeor more, and there is very little tolerance for incurring risk whiledeploying changes. All of these considerations introduce additionallevels of complexity, and thus data owners and hosting services mustmethodically migrate their cryptographic infrastructure toquantum-resistant cryptography. In addition, the cryptography transitionis challenging because it is not restricted only to algorithms and keylengths. Rather, the cryptography transition is impacted by severalother details of security infrastructure, such as interoperability,integration with existing systems and security architectures,scalability, compliance and regulatory requirements, maintenance, andbackward compatibility requirements.

In contrast to conventional cryptographic systems, the presentdisclosure relates to a post-quantum cryptography (PQC) system thatmitigates the vulnerability of traditional cryptographic algorithms byproviding techniques for migrating enormous volumes of data and complexIT systems to PQC technologies and platforms that are not vulnerable toattack by a quantum computer. The term “PQC” refers to cryptosystemswhich are, or are considered to be, resistant to attacks that use aquantum computer for cryptanalysis. In some embodiments, PQCcryptographic techniques include PQC communications channel-basedcryptographic techniques, hash-based PQC cryptographic techniques,lattice-based PQC cryptographic techniques, isogeny-based PQCcryptographic techniques, code-based PQC cryptographic techniques,multivariate-based PQC cryptographic techniques, zero-knowledge proofPQC cryptographic techniques, other suitable techniques, andcombinations thereof (e.g., combinations of PQC communicationschannel-based cryptographic techniques with hash-based, lattice-based,isogeny-based, code-based, multivariate-based, or zero-knowledge proofPQC cryptographic techniques).

PQC communications channel-based cryptographic techniques use PQCcommunications channels to secure transmission of sensitive orconfidential message data, such as Society for Worldwide InterbankFinancial Telecommunication (SWIFT) messages, International Organizationfor Standardization (ISO) 8583 messages, ISO 20022 messages, Internet ofThings (IoT) data, Health Insurance Portability and Accountability Act(HIPAA) data (e.g., electronic medical records, protected healthinformation), copyrighted content (e.g., electronic media, digitalrights management (DRM)-protected data files), and other suitablemessages. For example, the PQC system may be configured to implement aPQC communications protocol that transmits a first portion of anelectronic communication (e.g., message overhead data such as protocoloverhead, header data, metadata) to a client device over a firstclassical communications channel (e.g. non-PQC communications channel)and transmits a second portion of the electronic communication (e.g.,message payload data) to the client device over a second classicalcommunications channel (e.g., a PQC back channel such as a PQCout-of-band communications channel). In some embodiments, the firstclassical communications channel and the second classical communicationschannel may utilize different classical communications channels (e.g.,different communications networks, communications lines, communicationscircuitry, or a combination thereof). In some embodiments, the firstclassical communications channel and the second classical communicationschannel may utilize the same classical communications circuitry (e.g.,the same communications network, lines, hardware, infrastructure) but adifferent protocol, communications mechanism, network connector, orcombination thereof. For example, the PQC system may implement thenon-PQC communications channel as an in-band communications channel andthe PQC communications channel as an out-of-band communications channelusing the same communications infrastructure.

In one illustrative example, the electronic communication may be a SWIFTmessage, the first portion of an electronic communication may compriseSWIFT message overhead data, and the second portion of an electroniccommunication may comprise SWIFT message payload data. In anotherillustrative example, the first portion of the electronic communicationmay comprise a cryptographic data attribute indicative of a symmetriccryptographic technique, and the second portion of the electroniccommunication may comprise a symmetric cryptographic key, such as an AESsymmetric cryptographic key. The PQC system may be configured toauthenticate a session (e.g., perform a cryptographic handshake) withthe client device over the non-PQC communications channel based on thesymmetric cryptographic key that was transmitted to the client device,or a PQC add-on device coupled to the client device, over the PQCcommunications channel.

In yet another illustrative example, the first portion of the electroniccommunication may comprise a PQC indicator data structure thatidentifies the PQC communications channel and indicates that a secondportion of the electronic communication is to be transmitted over a PQCcommunications channel. The PQC indicator data structure may comprise alink or pointer to the PQC communications channel, a header thatidentifies the PQC communications channel as being out-of-band, otheridentification and routing information, or a combination thereof. Insome embodiments, the PQC indicator data structure may comprise a linkto the second portion of the electronic communication. In someembodiments, the first portion of the electronic communication maycomprise a TLS extension comprising the PQC indicator data structure. Inanother example, the first portion of the electronic communication maycomprise an ISO 8583 extension comprising the PQC indicator datastructure. In another example, the PQC indicator data structure may be,or comprise, or be indicated by, a PQC flag value. In another example,the PQC indicator data structure may comprise a link to a PQC electronicagreement (e.g., a bilateral agreement between the PQC system and theclient device to exchange confidential or sensitive data over a PQCcommunications channel) comprising the PQC indicator data structure.

In some embodiments, the PQC indicator data structure may comprise alink to a PQC shim configured to allow communication with the PQC system(e.g., via PQC callback circuitry comprised by the PQC system) over thePQC communications channel. For example, the PQC indicator datastructure may further comprise a PQC shim automatic installation controlsignal indicative of an electronic instruction for the client device toautomatically install the PQC shim based on the link. In anotherexample, the PQC indicator data structure may further comprise a PQCshim manual installation control signal indicative of an electronicinstruction for the client device to manually install the PQC shim basedon the link. In another example, the first portion of the electroniccommunication may comprise a PQC smart contract comprising the PQCindicator data structure.

In some embodiments, the first portion of the electronic communicationmay comprise a PQC request data structure (e.g., a request for anacknowledgment or confirmation that the client device is configured tocommunicate over a PQC communications channel). The PQC system may beconfigured to receive, in response to transmission of the PQC requestdata structure, a PQC acknowledgement data structure (e.g., anacknowledgment or confirmation that the client device is configured tocommunicate over a PQC communications channel) from the client deviceover the non-PQC communications channel. In response to receipt of thePQC acknowledgement data structure, to transmit the second portion ofthe electronic communication to the client device over the PQCcommunications channel.

In some embodiments, PQC indicator data structure may further identify aquantum communications channel and indicate that a quantum cryptographickey is to be transmitted over the quantum communications channel. ThePQC indicator data structure may comprise a link or pointer to thequantum communications channel, a header that identifies the quantumcommunications channel and comprises other identification and routinginformation. In some embodiments, the PQC indicator data structure maycomprise a link to the quantum cryptographic key. In some embodiments,the first portion of the electronic communication may comprise a TLSextension comprising the PQC indicator data structure. In anotherexample, the first portion of the electronic communication may comprisean ISO 8583 extension comprising the PQC indicator data structure. Inanother example, the PQC indicator data structure may be, or comprise,or be indicated by, a quantum flag value. In another example, the PQCindicator data structure may comprise a link to a quantum electronicagreement (e.g., a bilateral agreement between the PQC system and theclient device to exchange quantum information over the quantumcommunications channel) comprising the PQC indicator data structure.

In some embodiments, the first portion of the electronic communicationmay comprise a quantum request data structure (e.g., a request for anacknowledgment or confirmation that the client device is configured tocommunicate over a quantum communications channel). The PQC system maybe configured to receive, in response to transmission of the quantumrequest data structure, a quantum acknowledgement data structure (e.g.,an acknowledgment or confirmation that the client device is configuredto communicate over a quantum communications channel) from the clientdevice over the non-PQC communications channel. In response to receiptof the quantum acknowledgement data structure, the PQC system may beconfigured to transmit the quantum cryptographic key to the clientdevice over the quantum communications channel. Subsequently, the PQCsystem may be configured to authenticate a session (e.g., perform acryptographic handshake) with the client device over the non-PQCcommunications channel based on the quantum cryptographic key that wastransmitted to the client device over the quantum communicationschannel.

Hash-based PQC cryptographic techniques (e.g., hash-based PQCcryptographic signatures) are suitable for one-time use, wherein atuning parameter provides a trade-off between signature size and keygeneration, signing, and verification speed, and can be can be used withany secure hashing function. Hash-based PQC cryptographic techniques maybe used to provide digital signatures, such as Leighton-Micali Signature(LMS), eXtended Merkle Signature Scheme (XMSS), and SPHINCS+.

Lattice-based PQC cryptographic techniques are based on the shortestvector problem, the leading replacement for prime factorization anddiscrete logarithm, and typically are less computationally resourceintensive in relation to isogeny-based and other PQC cryptographictechniques. In some instances, lattice-based PQC cryptographictechniques may be used to provide digital signatures, such as Dilithiumand qTESLA. In some instances, lattice-based PQC cryptographictechniques may be used to provide key exchange by key encapsulation,such as NewHope, Frodo Key-Encapsulation Mechanisms (FrodoKEM), Nthdegree-Truncated polynomial Ring Units (NTRU) Prime, and Kyber. In someinstances, lattice-based PQC cryptographic techniques may be used toprovide key exchange by key agreement, such as NewHope Classic, FrodoDiffie-Hellman (FrodoDH), and Ring Learning With Errors Key EXchange(RLWE-KEX).

Isogeny-based PQC cryptographic techniques use very small keys andtypically are more computationally resource intensive in relation tolattice-based and other PQC cryptographic techniques. In some instances,isogeny-based PQC cryptographic techniques may be used to provide keyexchange by key encapsulation, such as Supersingular Isogeny KeyEncapsulation (SIKE). In some instances, isogeny-based PQC cryptographictechniques may be used to provide key exchange by key agreement, such asSupersingular isogeny Diffie-Hellman (SIDH) key exchange.

Code-based PQC cryptographic techniques use very large key sizes yet aretypically the fastest PQC cryptographic techniques at the comparablesecurity level (e.g., extremely fast in encryption and reasonably fastin decryption). In some instances, code-based PQC cryptographictechniques may be used to provide key exchange by key encapsulation,such as Classic McEliece, McEliece Quasi-Cyclic Moderate Density ParityCheck (QC-MDPC), and Bit Flipping Key Encapsulation (BIKE).

Multivariate-based PQC cryptographic techniques use small public keysand fast verification yet, in some instances, are less efficient thanother PQC cryptographic techniques. Multivariate-based PQC cryptographictechniques may be used to provide digital signatures, such as Rainbow.

Zero-knowledge proof PQC cryptographic techniques use very small keypairs and derive their security entirely from the security ofsymmetric-key primitives and are believed to be quantum-secure. In someinstances, zero-knowledge proof PQC cryptographic techniques may be usedto provide digital signatures, such as Picnic.

In some embodiments, the PQC system may retrieve one or more of thehash-based PQC cryptographic techniques, lattice-based PQC cryptographictechniques, isogeny-based PQC cryptographic techniques, code-based PQCcryptographic techniques, multivariate-based PQC cryptographictechniques, and zero-knowledge proof PQC cryptographic techniques from aremote server or data storage device, such as the ISARA toolkit, thelibOQS library, the libpqcrypto library, or a combination thereof.

It is to be understood that each PQC cryptographic technique may beimplemented as a variant of a PQC cryptographic algorithm (e.g., basedon NIST security level). For example, the libOQS implementation ofDilithium includes the variants Dilithium II (e.g.,Dilithium_II_Medium), Dilithium III (e.g., Dilithium_III_Recommended),and Dilithium IV (e.g., Dilithium_IV_VeryHigh); and the ISARA RadiateToolkit implementation of Dilithium includes the variants Dilithium 128and Dilithium 160. Accordingly, the PQC cryptographic technique for thePQC cryptographic algorithm “Dilithium” may be Dilithium II, DilithiumIII, Dilithium IV, Dilithium 128, or Dilithium 160. In yet anotherexample, the ISARA Radiate Toolkit implementation of FrodoKEM includesthe variants FrodoKEM-976-AES and FrodoKEM-976-C SHAKE. In yet anotherexample, the ISARA Radiate Toolkit speed-optimized implementation ofNewHope includes the variant Lattice-based Unique Key Exchange (LUKE).

In some embodiments, the present disclosure relates to a PQC systemconfigured to provide PQC migration for classical systems (e.g., non-PQCsystems) to utilize PQC cryptographic techniques and thereby mitigatevulnerabilities from quantum computers using Shor's algorithm,identification of techniques to reduce the attack surface ofcryptographic operations, and solutions to other cascading opportunitiesand challenges identified herein that stem from the vulnerability oftoday's common public-key encryption techniques to quantum computing.

In some embodiments, the present disclosure relates to a PQC systemconfigured to provide for, among other features disclosed herein: (i)generating a set of data attributes about received data for subsequentuse in determining a PQC cryptographic technique (including, but notlimited to, a PQC communications channel-based cryptographic technique)for encrypting, transmitting, and receiving data; (ii) generating a riskprofile data structure indicative of a vulnerability of received data ina PQC data environment for subsequent use in determining a PQCcryptographic technique for encrypting, transmitting, and receivingdata; (iii) generating a set of PQC encryption attributes for encrypting(including, but not limited to, signing with digital signatures),transmitting, and receiving data based on a set of data attributes aboutthe data, a risk profile data structure indicative of a vulnerability ofthe data in a PQC data environment, and PQC cryptographic performanceinformation associated with a set of PQC cryptographic techniques(including, but not limited to, a subset of PQC communicationschannel-based cryptographic techniques); and (iv) monitoring anenveloped data structure comprising data and a data envelope thatincludes a set of data attributes about the data and a risk profile datastructure indicative of a vulnerability of the data in a PQC dataenvironment. In some embodiments, in response to identifying a change inthe enveloped data structure, the PQC system provided herein maygenerate a second set of PQC encryption attributes for subsequentlyencrypting, transmitting, and receiving data based on the set of dataattributes, the risk profile data structure, and PQC cryptographicperformance information associated with a set of PQC cryptographictechniques. In some embodiments, the PQC system provided herein mayutilize a hybrid PQC cryptographic technique (e.g., hybrid PQCcryptographic technique={PQC cryptographic technique, Non-PQCcryptographic technique}; a PQC cryptographic technique and non-PQCcryptographic technique coexisting in the data envelope).

In one example embodiment implementing a PQC communicationschannel-based cryptographic technique, the PQC system may transmit afirst portion of an electronic communication (e.g., overhead data) to aclient device over a non-PQC communications channel. The PQC system mayfurther transmit a second portion of the electronic communication (e.g.,payload data) to the client device over a PQC communications channel.

In another example embodiment implementing a PQC communicationschannel-based cryptographic technique, the PQC system may transmit afirst portion of an electronic communication to a client device over anon-PQC communications channel. The PQC system may further transmit asecond portion of the electronic communication to a PQC add-on deviceover a PQC communications channel, wherein the PQC add-on device iscommunicatively coupled to the client device. In some embodiments, thePQC add-on device may comprise a PQC peripheral device communicativelycoupled (e.g., wireless, wired, electrically connected) to the clientdevice. In some embodiments, the PQC add-on device may comprise, or be,a PQC application specific integrated circuit (ASIC) installed within ahousing of the client device.

In yet another example embodiment implementing a PQC communicationschannel-based cryptographic technique, the PQC system may transmit afirst portion of an electronic communication to a client device over anon-PQC communications channel. The PQC system may further transmit aquantum cryptographic key to the client device over a quantumcommunications channel. The PQC system may further authenticate asession with the client device over the non-PQC communications channelbased on the quantum cryptographic key. In response to authentication ofthe session with the client device, the PQC system may transmit a secondportion of the electronic communication to the client device over a PQCcommunications channel.

In some embodiments, the present disclosure relates to a PQC systemconfigured to provide for receiving data and generating a set of dataattributes about the data. In some embodiments, the PQC system may befurther configured to provide for generating a data envelope based onthe set of data attributes. In some embodiments, the PQC system may befurther configured to provide for generating an enveloped data structurebased on the data envelope and the data.

In some embodiments, the present disclosure relates to a PQC systemconfigured to provide for receiving data and retrieving policyinformation associated with the data. In some embodiments, the PQCsystem may be further configured to provide for generating a set ofpolicy attributes about the data based on the data and the policyinformation. In some embodiments, the PQC system may be furtherconfigured to provide for generating a risk profile data structure basedon the set of policy attributes. The risk profile data structure may beindicative of a vulnerability of the data in a PQC data environment.

In some embodiments, the present disclosure relates to a PQC systemconfigured to provide for receiving data, a set of data attributes aboutthe data, and a risk profile data structure indicative of avulnerability of the data in a PQC data environment. In someembodiments, the PQC system may be further configured to provide forretrieving PQC cryptographic performance information associated with aset of PQC cryptographic techniques. The PQC cryptographic performanceinformation may comprise a set of PQC cryptographic performanceattributes for each PQC cryptographic technique in the set of PQCcryptographic techniques. In some embodiments, the PQC system may befurther configured to provide for generating a set of PQC encryptionattributes for encrypting the data based on the set of data attributes,the risk profile data structure, and the PQC cryptographic performanceinformation. In some embodiments, the PQC system may be furtherconfigured to provide for encrypting the data based on the set of PQCencryption attributes.

In some embodiments, the present disclosure relates to a PQC systemconfigured to provide adaptive PQC by monitoring an enveloped datastructure to identify a change in the enveloped data structure and, inresponse, determine whether to generate new PQC encryption attributesfor re-encrypting or double encrypting data contained in the envelopeddata structure. For example, the enveloped data structure may comprise adata envelope and data. The data envelope may comprise a set of dataattributes about the data and a risk profile data structure indicativeof a vulnerability of the data in a PQC data environment. The data mayhave been encrypted based on a first set of PQC encryption attributes.In some embodiments, the PQC system may be further configured to providefor generating an electronic indication of a change in the envelopeddata structure. In some embodiments, the PQC system may be furtherconfigured to provide for, in response to generating the electronicindication of the change in the enveloped data structure, retrieving PQCcryptographic performance information associated with a set of PQCcryptographic techniques. The PQC cryptographic performance informationmay comprise a set of PQC cryptographic performance attributes for eachPQC cryptographic technique in the set of PQC cryptographic techniques.In some embodiments, the PQC system may be further configured to providefor generating a second set of PQC encryption attributes for encryptingthe data based on the set of data attributes, the risk profile datastructure, the change in the enveloped data structure, and the PQCcryptographic performance information. In some embodiments, the PQCsystem may be further configured to provide for encrypting the databased on the second set of PQC encryption attributes.

In some embodiments, the present disclosure relates to a PQC systemconfigured to provide PQC cryptographic techniques by, as an initialprocess, determining characteristics about received data. For example,the PQC system may be configured to receive encrypted data withvariables, gather metadata about the data, and then determinecharacteristics about the data. In some embodiments, the characteristicsabout the data may include: (i) payload size (e.g., 30 page electronicmortgage document); (ii) complexity of the data based on metadata (e.g.,retention size, format); (iii) compliance requirements; (iv)classification; (v) time not to exceed (NTE) or time to live (TTL); (vi)information value and longevity; (vii) data value and longevity; (viii)frequency; (ix) scalability; (x) domain of the data; (xi) how was thedata encrypted (e.g., frequency analysis); any other suitable data; andany combination thereof. Subsequently, the PQC system may be configuredto transmit the determined characteristics about the data for use as aninput in selecting a PQC cryptographic technique, key size, and mode ofoperation for re-encrypting the data based on allowable transactiontime.

In some embodiments, the present disclosure relates to a PQC systemconfigured to provide PQC cryptographic techniques by, as anintermediate process, identifying a risk profile about received data.For example, the PQC system may be configured to receive encrypted datawith variables, gather policy data about the data (e.g., pullscompliance requirements), and then generate a risk profile about thedata indicative of a level of risk of the data in a PQC environment. Insome embodiments, the policy data about the data may include: (i)compliance requirements; (ii) policies; (iii) regulations; (iv)regulatory classifications; (v) industry; (vi) time to quantum computingthreat; and (vii) dependencies on the encryption level; any othersuitable data; and any combination thereof. In some embodiments, therisk profile data structure may include: (a) a vulnerability score; (b)an indication of where vulnerabilities lie; (c) an indication of why thevulnerability score is what it is; (d) an indication of whether the datais in compliance with the compliance requirements; (e) the percentage ofcompliance with the compliance requirements; any other suitable data;and any combination thereof. Subsequently, the PQC system may beconfigured to transmit the generated risk profile about the data for useas an input in selecting a PQC cryptographic technique, key size, andmode of operation for re-encrypting the data based on allowabletransaction time.

In some embodiments, the present disclosure relates to a PQC systemcomprising, or communicatively coupled to, a quantum computing (QC)detection system configured to provide for QC detection (e.g., thedetection of a quantum computer and determination of its capabilities,such as its capability to compromise various cryptographic techniques)by, among other features disclosed herein, generating QC detection data(e.g., fictitious data), encrypting the QC detection data based on acryptographic technique (e.g., a non-PQC cryptographic technique, oreven a PQC cryptographic technique or a hybrid PQC cryptographictechnique), and monitoring a set of data environments (e.g., internaldata environments, external data environments) for electronicinformation related to the encrypted QC detection data. For example, theQC detection system may be configured to provide for generating a pairof asymmetric cryptographic keys comprising a public cryptographic keyand a private cryptographic key, generating encrypted QC detection databased on the pair of asymmetric cryptographic keys, and destroying theprivate cryptographic key. In another example, the QC detection systemmay be configured to provide for generating encrypted QC detection databased on a PQC cryptographic technique that, in some instances, does nothave public or private cryptographic keys. The QC detection system mayuse QC detection data encrypted based on the PQC cryptographic techniqueto detect new algorithms (e.g., other than Shor's algorithm or Grover'salgorithm) that renders that PQC cryptographic technique breakable by aquantum computer or some yet-to-be-discovered technology.

In some embodiments, the QC detection system may be configured toprovide for QC detection for use in migration to systems that utilizePQC cryptographic techniques that mitigate vulnerabilities from quantumcomputers using Shor's algorithm or Grover's algorithm, identificationof techniques to reduce the attack surface of cryptographic operations,and solutions to other cascading opportunities and challenges identifiedherein that stem from the vulnerability of today's common public-keyencryption techniques to quantum computing. In some embodiments, thepresent disclosure relates to a QC detection system configured toprovide for QC detection using, among other features described herein:(i) a QC detection technique based on a digital signature (e.g., an RSAdigital signature), wherein the QC detection system destroys the privatecryptographic key but retains the public cryptographic key; (ii) a QCdetection technique based on a pair of asymmetric cryptographic keys(e.g., an RSA key pair) generated based on a symmetric cryptographic key(e.g., an AES key), wherein the QC detection system destroys the privatecryptographic key but retains the public cryptographic key; (iii) a QCdetection technique based on a symmetric cryptographic key (e.g., an AESkey) generated based on a pair of asymmetric cryptographic keys (e.g., aDH key pair), wherein the QC detection system destroys both of theasymmetric cryptographic keys; (iv) a QC detection technique based onmultiple different cryptographic techniques (e.g., RSA, DH, ECDH, AES)having staggered key sizes (e.g., RSA-2048, RSA-3072, DH-2048, DH-3072,ECDH-256, ECDH-521, AES-128, AES-256); any other suitable QC detectiontechnique; or any combination thereof.

In some embodiments, the QC detection system may be further configuredto provide for monitoring a set of data environments for electronicinformation related to the encrypted QC detection data. The monitoringof the set of data environments may comprise internal monitoring ofinternal data environments (e.g., internal information systems, internaldata networks, internal data storage devices), external monitoring ofexternal data environments (e.g., content delivery networks (CDNs),cloud service platforms, social media platforms, dark websites), andhybrid monitoring of hybrid data environments (e.g., combinations ofinternal and external data networks).

In some embodiments, the QC detection system may be further configuredto provide for monitoring the set of data environments in anelectronically subtle and delicate way to preserve secrecy to mitigateor eliminate the risk that the monitoring will tip anyone off and renderthe fake data radioactive to QC hackers. In some embodiments, the QCdetection system may be further configured to provide for monitoring theset of data environments using data monitoring circuitry that, in someinstances, is not vulnerable to an attack that sets off a false alarm.For example, the QC detection system may generate and monitor a databaseof QC detection data. However, hacking of that database could enable theQC detection data to be used without compromising the cryptographictechnique (e.g., RSA) with which the QC detection data was encrypted. Asa result, the QC detection system might incorrectly assume that thecryptographic technique was compromised when in fact it was not. The QCdetection system may solve this problem as shown in the followingexamples.

In one illustrative example embodiment, to detect the QC detection datawithout storing it anywhere, the QC detection system may encrypt the QCdetection data using an asymmetric cryptographic technique, destroy theprivate cryptographic key, and then monitor for the subsequent use ofthe private cryptographic key. Because the QC detection system destroyedthe private cryptographic key, the private cryptographic key could onlybe used again by using QC to reverse engineer the private cryptographickey from the public cryptographic key, proving the existence of a QCthreat capable of compromising the cryptographic technique. In anotherillustrative example embodiment, to detect the QC detection data withoutstoring it anywhere, the QC detection system may encrypt the QCdetection data using a symmetric cryptographic technique and mitigatethe risk of an attack that sets off a false alarm through heightenedsecurity of the database of QC detection data.

In some embodiments, the QC detection system may be further configuredto provide for detecting the electronic information related to theencrypted QC detection data and generating a QC detection alert controlsignal in response detecting the electronic information related to theencrypted QC detection data.

In some embodiments, the present disclosure relates to a PQC systemconfigured to provide PQC cryptographic techniques by, as a near-finalprocess, optimizing PQC cryptographic parameters (e.g., selecting anoptimal PQC cryptographic technique, key size, and mode of operation)for re-encrypting received encrypted data. For example, the PQC systemmay be configured to receive encrypted data with variables, receivecharacteristics about the data, receive a risk profile about the data,gather performance metrics about available PQC cryptographic techniques,and then optimize the PQC cryptographic parameters (e.g., select anoptimal PQC cryptographic technique, key size, and mode of operation;tune various parameters and characteristics of various implementationsof PQC cryptographic techniques) for re-encrypting the data based on thecharacteristics about the data, the risk profile about the data, theperformance metrics about the available PQC cryptographic techniques,and an allowable transaction time (e.g., NTE, TTL). The performancemetrics may include: (i) central processing unit (CPU) utilization; (ii)memory utilization; (iii) latency; (iv) time for operation; (v) keysize; (vi) crypto strength (e.g., NIST level); (vii) data size (e.g.,sig, data block); (viii) PQC cryptographic technique footprint; anyother suitable data; and any combination thereof. In some instances, thePQC system may be configured to optimize the PQC cryptographicparameters using artificial intelligence or machine learning techniques.For example, the PQC system may tune various parameters andcharacteristics of various implementations of PQC cryptographictechniques. Subsequently, the PQC system may be configured to re-encryptthe data based on the optimal PQC cryptographic parameters.

In some embodiments, the present disclosure relates to a PQC systemconfigured to provide for adaptive PQC data encryption techniques. Forexample, the PQC system may be configured to dynamically upgrade anddowngrade (e.g., throttle) a PQC cryptographic technique used to encryptdata. In some instances, the PQC system may be configured to dynamicallyoptimize the PQC cryptographic parameters (e.g., dynamically select anoptimal PQC cryptographic technique, key size, and mode of operation) tooptimize for risk, performance, or information value and longevity,while satisfying temporal requirements (e.g., allowable transactiontime, NTE, TTL). For example, during a first duration of time, the PQCsystem may be configured to dynamically optimize the PQC cryptographicparameters to optimize for risk; and during a second duration of time,the PQC system may be configured to dynamically optimize the PQCcryptographic parameters to optimize for performance; and during a thirdduration of time, the PQC system may be configured to dynamicallyoptimize the PQC cryptographic parameters to optimize for informationvalue and longevity. In another example, the PQC encryption strength mayincrease or decrease based on the sensitivity (e.g., confidentiality,value, vulnerability, data classification level) of the data. In someinstances, the PQC system may be configured to provide nested PQCcryptographic techniques by, for example, utilizing multiple levels ofencryption on a data envelope's data as the encryption techniquesevolve.

In some embodiments, the PQC system may be configured to receive a QCdetection alert control signal and, in response, dynamically upgrade thePQC cryptographic technique used to encrypt data based on the QCdetection alert control signal. For example, if the QC detection alertcontrol signal indicates that a particular cryptographic technique hasbeen compromised by a quantum computer, the PQC system may be configuredto provide for re-encrypting data using a PQC cryptographic techniquehaving a cryptostrength that cannot be compromised by that particularquantum computer.

There are many advantages of these and other embodiments describedherein, such as: facilitating migration to quantum-resistant informationsystems that utilize PQC cryptographic techniques that cannot becompromised by a quantum computer; detecting real world QC capabilitiesfor use in facilitating adaptive migration to quantum-resistantinformation systems that utilize PQC cryptographic techniques thatcannot be compromised by a realized quantum computer; facilitatingfaster, cheaper, and less computing resource and data intensiveprocesses for providing identification of techniques to reduce theattack surface of cryptographic operations; detecting QC capabilitiesfor use in facilitating adaptive migration to quantum-resistantinformation systems that utilize PQC cryptographic techniques thatcannot be compromised by a realized quantum computer; and providing newways to solve the cascading opportunities and challenges identifiedherein that stem from a sudden vulnerability to today's commonpublic-key encryption techniques arising from the realization of quantumcomputing. Among other features, these and other embodiments describedherein at least: reflect improvements in the functioning of computingsystems or devices, such as PQC systems (including but not limited toPQC server devices and databases), server devices, client devices, andcombinations thereof; reflect improvements to other technologies ortechnical fields as described herein (e.g., PQC, QC detection); andeffect transformations or reductions of particular articles to differentstates or things, such as unencrypted data and data structures,encrypted data and data structures, electronic signals, quantum signals,other articles described herein, and combinations thereof.

Definitions

As used herein, the terms “data,” “content,” “information,” “electronicinformation,” “signal,” “command,” and similar terms may be usedinterchangeably to refer to data capable of being transmitted, received,and/or stored in accordance with embodiments of the present disclosure.Thus, use of any such terms should not be taken to limit the spirit orscope of embodiments of the present disclosure.

The term “comprising” means “including, but not limited to.” The termcomprising should be interpreted in the manner it is typically used inthe patent context. Use of broader terms such as comprises, includes,and having should be understood to provide support for narrower termssuch as consisting of, consisting essentially of, and comprisedsubstantially of.

The phrases “in one embodiment,” “according to one embodiment,” and thelike generally mean that the particular feature, structure, orcharacteristic following the phrase may be included in at least oneembodiment of the present disclosure and may be included in more thanone embodiment of the present disclosure (importantly, such phrases donot necessarily refer to the same embodiment).

The word “example” is used herein to mean “serving as an example,instance, or illustration.” Any implementation described herein as“example” is not necessarily to be construed as preferred oradvantageous over other implementations.

If the specification states a component or feature “may,” “can,”“could,” “should,” “would,” “preferably,” “possibly,” “typically,”“optionally,” “for example,” “often,” or “might” (or other suchlanguage) be included or have a characteristic, that particularcomponent or feature is not required to be included or to have thecharacteristic. Such component or feature may be optionally included insome embodiments, or it may be excluded.

The terms “processor” and “processing circuitry” are used herein torefer to any programmable microprocessor, microcomputer or multipleprocessor chip or chips that can be configured by software instructions(applications) to perform a variety of functions, including thefunctions of the various embodiments described above. In some devices,multiple processors may be provided, such as one processor dedicated towireless communication functions and one processor dedicated to runningother applications. Software applications may be stored in the internalmemory before they are accessed and loaded into the processors. Theprocessors may include internal memory sufficient to store theapplication software instructions. In many devices the internal memorymay be a volatile or nonvolatile memory, such as flash memory, or amixture of both. The memory may also be located internal to anothercomputing resource (e.g., enabling computer readable instructions to bedownloaded over the Internet or another wired or wireless connection).

For the purposes of this description, a general reference to “memory”refers to memory accessible by the processors including internal memoryor removable memory plugged into the device, remote memory (e.g., cloudstorage), and/or memory within the processors themselves. For instance,memory may be any non-transitory computer readable medium havingcomputer readable instructions (e.g., computer program instructions)stored thereof that are executable by a processor.

The term “computing device” is used herein to refer to any one or all ofprogrammable logic controllers (PLCs), programmable automationcontrollers (PACs), industrial computers, desktop computers, personaldata assistants (PDAs), laptop computers, tablet computers, smart books,palm-top computers, personal computers, smartphone, headset, smartwatch,and similar electronic devices equipped with at least a processorconfigured to perform the various operations described herein. Devicessuch as smartphones, laptop computers, tablet computers, headsets, andsmartwatches are generally collectively referred to as mobile devices.

The term “server” or “server device” is used to refer to any computingdevice capable of functioning as a server, such as a master exchangeserver, web server, mail server, document server, or any other type ofserver. A server may be a dedicated computing device or a computingdevice including a server module (e.g., an application which may causethe computing device to operate as a server). A server module (e.g.,server application) may be a full function server module, or a light orsecondary server module (e.g., light or secondary server application)that is configured to provide synchronization services among the dynamicdatabases on computing devices. A light server or secondary server maybe a slimmed-down version of server type functionality that can beimplemented on a computing device, such as a smart phone, therebyenabling it to function as an Internet server (e.g., an enterprisee-mail server) only to the extent necessary to provide the functionalitydescribed herein.

The term “post-quantum cryptography (PQC)” refers to cryptosystems whichare, or are considered to be, resistant to quantum attacks. In someinstances, the term PQC refers to cryptography that may or will besecure even after the development of large-scale error tolerant quantumcomputing devices. The related term “PQC migration” refers to themigration of data encrypted using classical systems to be encryptedusing quantum-resistant algorithms and includes, but is not limited to,the updating of system software stacks and security infrastructure. Insome embodiments, PQC migration includes migration of classical systemsto PQC systems or hybrid systems (e.g., a combination of classical andPQC). In some embodiments, PQC migration includes translations ofnetworks. For example, today networks A, B, and C may only be able toutilize classic cryptography, but tomorrow network C may be able toutilize PQC so the PQC system may drop in a PQC gateway to translateback and forth such that eventually network B is PQC enabled, butnetwork A may never become PQC enabled so the PQC system may determinethat transactions to or from network A are a higher risk and implementthe PQC cryptographic techniques described herein according to thathigher risk.

The term “quantum computing (QC) detection data” refers to dataconfigured to be used by the PQC system, or a QC detection systemcomprised by or in communication with the PQC system, to detect theexistence and capabilities of quantum computing and, in some instances,the strength of that quantum computing. In some instances, the PQCsystem may comprise fictitious data, such as fictitious account data, afictitious code-signing certificate, any other suitable data, or anycombination thereof. For example, the QC detection data may comprisefictitious financial account data, a fictitious electronic mortgagedocument, a fictitious electronic deed, a fictitious electronic loandocument (e.g., a fictitious auto loan document, a fictitious personalloan document), a fictitious electronic stock transfer agreement,fictitious identity information, fictitious medical data, fictitiouscredit card data, any other suitable data, or any combination thereof.The fictitious identity information may comprise, for example, afictitious name, address, phone number, email address, social securitynumber, driver license number, any other suitable information, or acombination thereof. The fictitious credit card data may comprise, forexample, a fictitious credit card number, credit card issuer (e.g.,financial institution), cardholder name, cardholder billing address,expiration date, card verification value (CVV) security code, creditcard network (e.g., Visa, MasterCard, American Express), EMV chip data,magnetic stripe data, etc.), any other suitable information, or acombination thereof. In another example, the QC detection data maycomprise a fictitious code-signing certificate, a fictitious emailcertificate, a fictitious legally binding electronic signaturecertificate that represents the digital identity of a signer (e.g., adigital identification (ID) certificate, such as an X.509 certificate),any other suitable information, or a combination thereof.

The term “data environment” refers to internal data environments,external data environments, hybrid data environments, any other suitableenvironment, or any combination thereof. The internal data environmentsmay comprise, for example, internal information systems, internal datanetworks, internal data storage devices, any other suitable dataenvironment, or any combination thereof. The external data environmentsmay comprise, for example, content delivery networks (CDNs), cloudservice platforms, social media platforms, dark websites, any othersuitable data environment, or any combination thereof. For example, theexternal data environments may comprise a set of websites, such as a setof social media platforms, public websites (e.g., document leakswebsites), online repositories (e.g., online file storage andsynchronization services, online file hosting services), P2P filesharing networks (e.g., BitTorrent), deep websites, dark websites (e.g.,onion addresses that end in the top level domain “.onion”), the MortgageElectronic Registration System (MERS), CDNs (including, but not limitedto, meta-CDNs), cloud service platforms, any other suitable dataenvironment, or any combination thereof.

The term “quantum basis” refers to sets of orthogonal quantum states,including, but not limited to, pairs of photonic polarization states.The pairs of photonic polarization states may comprise, for example, therectilinear, diagonal, and circular photonic polarization states. The“rectilinear basis” refers to the pair of rectilinear photonicpolarization states comprising the horizontal photon polarization state|0> and the vertical photon polarization state |1>. The “diagonal basis”refers to the pair of diagonal photonic polarization states comprisingthe diagonal photon polarization state of 45 degrees and the diagonalphoton polarization state 135 degrees. The “circular basis” refers tothe pair of circular photonic polarization states comprising the leftcircular photon polarization state |L> and the right circular photonpolarization state |R>.

The term “quantum particle” refers to photons, atoms, electrons,molecules, ions, or other suitable particles or quasi-particles (e.g.,composite fermions). The term “entangled quantum particle” refers to twoor more photons, atoms, electrons, molecules, ions, or other suitableparticles or quasi-particles entangled according to the principles ofquantum entanglement.

The term “qubit” refers to a basic unit of quantum informationcomprising a two-state, or two-level, quantum mechanical system, suchas: the polarization of a single photon (e.g., a photon encoded using aquantum basis as previously defined); the spin of a single electron(e.g., a spin qubit comprising the spin up state |1> and the spin downstate |0>); the energy level of a single atom (e.g., a superconductingqubit); the Hall conductance of electron systems (e.g., qubits based ona quantum Hall effect, such as an integer quantum Hall effect, afractional quantum Hall effect, or a quantum spin Hall effect); thevibration state of a single carbon nanotube or nanoparticle (e.g., acarbon qubit, a carbon nanotube or nanoparticle coupled to a spin qubit,a carbon nanotube or nanoparticle coupled to a superconducting qubit);the electronic state of an ion (e.g., a trapped ion); a transmissionline shunted plasma oscillation qubit (e.g., a fixed-frequency transmonqubit, a frequency-tunable transmon qubit); a charge qubit (e.g., asuperconducting charge qubit); a defect (e.g., a vacancy, a dopant, or acombination thereof, such as a nitrogen-vacancy center or asilicon-vacancy center) in a diamond structure (e.g., a diamond qubit);or any other suitable qubit. Qubits may exist in multiple statessimultaneously and can be made of any suitable quantum particle,including entangled quantum particles. Qubits may exist in multiplestates simultaneously and may be made of quantum particles such asphotons, atoms, electrons, molecules, ions, or other suitable particles,such as quasi-particles. In some embodiments, qubits may be entangledaccording to the principles of quantum entanglement. For example, a pairof entangled qubits may comprise a first entangled qubit and a secondentangled qubit, where measurement of the first entangled qubit causesthe collapse of the second entangled qubit such that the first entangledqubit and the second entangled qubit are equal (e.g., both “0” or both“1”) when measured using the same quantum basis.

The term “optical line” refers to an optical communications path. Forexample, an optical line may comprise an optical fiber, an opticalwaveguide, a fiberoptic cable, a non-polarization maintaining opticalfiber, an optical transmission line, a quantum line, or a combinationthereof. The term optical line broadly encompasses on-chip opticallines.

The term “quantum line” refers to a quantum communications path. Forexample, a quantum line may comprise a polarization-maintaining (PM)optical fiber (PMF or PM fiber), photonic transmission lines, photoniccrystals, photonic circuitry, free space (e.g., air, vacuum), or acombination thereof. In some embodiments, a PM fiber uses birefringenceto maintain the polarization states of photons. This is normally done bycausing consistent asymmetries in the PM fiber. Example PM fiber typesinclude: panda fiber which is used in telecom; elliptical clad fiber;and bowtie fiber. Any of these three designs uses birefringence byadding asymmetries to the fiber through shapes and stresses introducedin the fiber. This causes two polarization states to have differentphase velocities in the fiber. As such, an exchange of the overallenergy of the two modes (polarization states) becomes practicallyimpossible. The term optical line broadly encompasses on-chip quantumlines.

The term “on-chip encoder” and “on-chip decoder” is used herein to referto any device that respectively encodes or decodes a qubit ofinformation, or in time-bins of information, on a photon or an electron.In this regard, the qubit decoder may comprise an optoelectronic deviceas described below.

The terms “optoelectronic device,” “optoelectronic component,” “laserdevice,” “light source,” “single photon source,” “particle source,” andsimilar terms are used herein interchangeably to refer to any one ormore of (including, but not limited to, combinations of): a polarizedlight modulator (PLM); a polarized light demodulator (PLD); aquantization circuit; a laser device, such as a diode laser, a verticalcavity surface emitting laser (VCSEL), a semiconductor laser, afiberoptic laser, or an edge-emitting laser (e.g., a gallium arsenide(GaAs) edge-emitting laser comprising an indium gallium arsenide(InGaAs) quantum well); a light source; a single photon source; amodulator or modulating circuit; a photodetector device, such as aphotodetector, an array of photodetectors, or a photodetector panel; alight emitting device, such as a light emitting diode (LED), an array ofLEDs, an LED panel, or an LED display; a sensing device, such as one ormore sensors; any other device equipped with at least one of thematerials, structures, or layers described herein; an optical component,such as an optical lens, attenuator, deflector, phase shifter, filter,mirror, window, diffuser, prism, lenses, crystals (e.g., non-linearcrystals), wave plates, beam splitter, bit manipulator, polarizer, ordiffraction grating; an interferometer implemented as a Mach-Zehnderinterferometer (MZI), Fabry-Perot interferometer, Michelsoninterferometer, any other suitable configuration, or any combination orpermutation thereof; any device configured to function as any of theforegoing devices; or any combination thereof. In some embodiments, thelaser device may use a VCSEL to generate photons, qubits (e.g., bymodulating photons), or both. In some embodiments, a polarization pulseshaper may be integrated with the laser chip on the same laser device.In some embodiments, modulating circuitry (e.g., a modulating circuit)may be implemented on a board. Examples of a laser device may comprise afiberoptic laser with a polarizing component, an edge-emitting laser, aVCSEL, a PLM, or any other suitable device. In some embodiments, thelaser may generate photons, qubits, or both in the infrared ornear-infrared range (e.g., 1550 nanometers (nm), 980 nm, 900 nm). Forexample, a laser device may be an edge-emitting laser chip having afootprint smaller than one square millimeter and a thickness less than afew micrometers (microns) and comprising a gallium arsenide (GaAs)-basededge-emitting laser, a modulating circuit, and an attenuator ordeflector. Each of the MZIs disclosed herein may comprise a combinationof mirrors, beam splitters, photodetectors fiberoptic cables, lenses,nonlinear crystals, wave plates, motors (e.g., servo motors), motioncontrollers (e.g., servo motor controllers), temperature controllers(e.g., thermoelectric devices), and any other suitable componentsarranged to perform the operations and functions disclosed herein,including, but not limited to, the controlling of optical path length.In some embodiments, a first optoelectronic device may include aparticle source configured to generate single particles (e.g., photonsor electrons) and transmit the generated particles through a double-slitstructure to a first electron detector (e.g., “|1>”) and a secondelectron detector (e.g., “|0>”) as described herein.

The terms “security shelf-live,” “migration time,” and “collapse time”refer to the parameters shown below in Table 2:

TABLE 2 Example parameters that may be used by the PQC system describedherein to generate quantum computing threat assessments and electronicrecommendations associated therewith. Parameter Description Definition xSecurity shelf- Duration (e.g., in years) to keep the life (e.g., datacryptographic keys secure (e.g., “How long retention do you need yourcryptographic keys to requirement) remain secure?”) y PQC migrationEstimated duration (e.g., in years) to migrate time existinginfrastructure to a PQC system (e.g., “How long will it take to deploy aset of cryptography tools that are quantum- resistant?”) z Collapse timeEstimated duration (e.g., in years) to build a (e.g., time tolarge-scale quantum computer (e.g., “How quantum long will it be beforea quantum computer, computing or some other method, compromises thethreat) currently deployed public-key cryptography tools?”)

The term “security shelf-life” includes, but is not limited to, dataretention requirements. For example, in some instances the securityshelf life x of a piece of data may be based on governmental risk andregulatory requirements, such as the FDIC's data retention requirementsshown in Table 1.

The term “collapse time” includes, but is not limited to, time toquantum computing threat. The phrases “time to quantum computing threat”and “a time to a quantum computing threat” refer to an approximate timeto a quantum computing threat. In some instances, the collapse time zmay decrease when the PQC system identifies, or receives, technologicaladvancements relating to quantum computing; increased vulnerabilities tocryptographic techniques (e.g., one or more non-PQC cryptographictechniques, PQC cryptographic techniques, or hybrid PQC cryptographictechniques); or a QC detection alert control signal indicating that aparticular cryptographic technique (e.g., a non-PQC cryptographictechnique, a PQC cryptographic technique, a hybrid PQC cryptographictechnique) has been compromised by quantum computing. In oneillustrative, non-limiting example, the collapse time z may indicate anestimated 15% chance of compromising RSA-2048 by 2026 and an estimated50% chance of compromising RSA-2048 by 2031.

The term “control signal” refers to an electronic alert, notification,flag, or control signal configured to instruct, or cause, the PQCsystem, or a QC detection system comprised by or in communication withthe PQC system, to perform an automated process or function without userinteractivity. For example, control signals as described herein maycomprise QC detection alert control signals, leakage alert controlsignals, and tampering alert control signals. In some embodiments, a QCdetection alert control signal may indicate, for example, that aparticular cryptographic technique (e.g., a non-PQC cryptographictechnique, a PQC cryptographic technique, a hybrid PQC cryptographictechnique) used to encrypt or otherwise generate encrypted QC detectiondata has been compromised by quantum computing. In some embodiments, aleakage alert control signal may indicate, for example, the existence ofa data leakage event associated with QC detection data stored in aninternal data environment that was never transmitted outside of thatinternal data environment. In some embodiments, a tampering alertcontrol signal may indicate, for example, the existence of a datatampering event associated with QC detection data, wherein the QCdetection data has been altered but signed using the same digitalsignature. In some embodiments, the QC detection alert control signals,leakage alert control signals, tampering alert control signals, or acombination thereof may instruct, or cause, the PQC system to initiateautomated analyses and processes to mitigate the quantum computingthreat within a duration of time. In some instances, the PQC system maygenerate a control signal in accordance with the criteria discussedbelow with reference to Table 3.

The term “non-PQC cryptographic technique” refers to a cryptographictechnique that is not quantum-resistant. Non-PQC cryptographictechniques may comprise, for example, RSA, DH, and other such non-PQCcryptographic algorithms. In some instances, a non-PQC cryptographictechnique may be a variant of a non-PQC cryptographic algorithm. Forexample, a first non-PQC cryptographic technique may be RSA-2048, asecond non-PQC cryptographic technique may be RSA-3072, and a thirdnon-PQC cryptographic technique may be RSA-4096, each of which is adifferent variant of the same non-PQC cryptographic algorithm (e.g.,RSA). In another example, a first non-PQC cryptographic technique may beAES-128, and a second non-PQC cryptographic technique may be DH-2048,each of which is a variant of a different non-PQC cryptographicalgorithm (e.g., AES, DH). In yet another example, a first non-PQCcryptographic technique may encrypt overhead data based on RSA-2048 andtransmit the encrypted data over a non-PQC communications channel (e.g.,an in-band communications channel), and a second non-PQC cryptographictechnique may transmit overhead data over a non-PQC communicationschannel as clear text, each of which is a different variant of a non-PQCcommunications channel-based cryptographic technique.

The term “PQC cryptographic technique” refers to a quantum-resistantcryptographic technique. Generally, the families of PQC cryptographictechniques include key management and signature. PQC cryptographictechniques may comprise, for example, hash-based PQC cryptographictechniques, lattice-based PQC cryptographic techniques, isogeny-basedPQC cryptographic techniques, code-based PQC cryptographic techniques,multivariate-based PQC cryptographic techniques, zero-knowledge proofPQC cryptographic techniques, PQC communications channel-basedcryptographic techniques, and other suitable techniques. In someinstances, a PQC cryptographic technique may be a variant of a PQCcryptographic algorithm. For example, a first PQC cryptographictechnique may be Dilithium II, a second PQC cryptographic technique maybe Dilithium II, and a third PQC cryptographic technique may beDilithium 128, each of which is a different variant of the same PQCcryptographic algorithm (e.g., Dilithium). In another example, a firstPQC cryptographic technique may be LUKE, and a second PQC cryptographictechnique may be Dilithium II, each of which is a variant of a differentPQC cryptographic algorithm (e.g., NewHope, Dilithium). In yet anotherexample, a first PQC cryptographic technique may encrypt payload databased on Dilithium II and transmit the encrypted data over a PQCcommunications channel (e.g., a PQC back channel), and a second PQCcryptographic technique may generate a secret key that is used toencrypt payload data based on AES-256 and transmit the encrypted dataover a PQC communications channel, each of which is a different variantof a PQC communications channel-based cryptographic technique.

The term “hybrid PQC cryptographic technique” refers to a cryptographictechnique that comprises a non-PQC cryptographic technique and a PQCcryptographic technique. For example, a hybrid PQC cryptographictechnique may comprise a PQC cryptographic technique and non-PQCcryptographic technique coexisting in a data envelope, as defined by thestatement “hybrid PQC cryptographic technique={PQC cryptographictechnique, Non-PQC cryptographic technique}.” In some embodiments, ahybrid PQC cryptographic technique may comprise a hybrid PQCcryptographic mode, such as a signature-based hybrid PQC cryptographicmode consisting of a non-PQC cryptographic signature and a PQCcryptographic signature. In some embodiments, the hybrid PQCcryptographic mode is valid only if both the non-PQC cryptographicsignature and the PQC cryptographic signature are valid. For example,the PQC system may (i) validate the non-PQC cryptographic signatureaccording to the Federal Information Processing Standard (FIPS)publication 140 (e.g., 140-1, 140-2, 140-3); and (ii) validate the PQCcryptographic signature using multiple public-key algorithms for X.509certificates, such as quantum-resistant X.509 Multiple Public KeyAlgorithm Certificates.

The term “quantum cryptographic technique” refers to a quantumparticle-based cryptographic technique. Quantum cryptographic techniquesmay comprise, for example, quantum key distribution (QKD) techniques,quantum coin flipping protocols, quantum commitment protocols, quantumoblivious transfer protocols, and other suitable techniques. In someinstances, a quantum cryptographic technique may be a variant of aquantum cryptographic algorithm. For example, a first quantumcryptographic technique may be a BB84-based QKD technique, a secondquantum cryptographic technique may be an E91-based QKD technique, and athird quantum cryptographic technique may be a KMB09-based QKDtechnique, each of which is a different variant of the same quantumcryptographic algorithm (e.g., QKD).

The term “non-PQC communications channel” refers to a communicationschannel (e.g., a wired or wireless communications channel) over whichnon-quantum data and signals are exchanged using one or more non-PQCcryptographic techniques that do not themselves directly rely on quantumproperties. For example, the PQC system described herein may implement anon-PQC communications channel by encrypting data based on a non-PQCcryptographic technique (e.g., RSA) and then transmitting the encrypteddata over a non-PQC communications channel (e.g., an “in-band”communications channel) or, in some instances, by transmittingunencrypted, clear text data over the non-PQC communications channel. Insome embodiments, a non-PQC communications channel may be a classicalcommunications channel derived from a shared secret that is derivedusing a non-PQC cryptographic technique, such as a shared secretgenerated using DH.

The term “PQC communications channel” refers to a communications channel(e.g., a wired or wireless communications channel) over whichnon-quantum data and signals are exchanged using one or more PQCcryptographic techniques (e.g., for authentication, encryption, or both)that do not themselves directly rely on quantum properties. For example,the PQC system described herein may implement a PQC communicationschannel by encrypting data based on a PQC cryptographic technique (e.g.,Dilithium II) and then transmitting the encrypted data over a classicalback channel (e.g., an “out-of-band” communications channel). In someembodiments, a PQC communications channel may be based on an underlyingKey Encapsulation Mechanism or Key Agreement Scheme. In someembodiments, a PQC communications channel may use a Key EncapsulationMechanism (e.g., SIKE, NTRUPrime, Kyber) to encapsulate a shared secretand ensure its safe transmission between Alice and Bob. This sharedsecret subsequently will either (i) be used as a Symmetric Key (e.g.,for Symmetric Key encryption) or (ii) be handed over to a Key DerivationFunction to generate a shared encryption key. In some embodiments, a PQCcommunications channel may use a Key Agreement Scheme (e.g., SIDH,NewHopeDH) may allow both Alice and Bob to calculate the shared secretbased on public parameters and public key that they exchange. Unlike KeyEncapsulation Mechanisms, Key Agreement Schemes do not encapsulate thecalculated shared secret with cipher text. Key Agreement Schemes may beextended to generate Ephemeral keys. In some instances, after the sharedsecret is calculated, the keys are destroyed to preserve perfect forwardsecrecy. In some embodiments, a PQC communications channel may be aclassical communications channel derived from a shared secret that isderived using a Key Encapsulation Mechanism or a Key Agreement Scheme.

The term “quantum communications channel” refers to a quantumcommunications channel (e.g., an optical line, a quantum line) overwhich quantum data and particles, such as qubits, are exchanged usingone or more quantum cryptographic techniques (e.g., QKD) that directlyrely on quantum properties, such as quantum uncertainty, quantumentanglement, or both.

Having set forth a series of definitions called-upon throughout thisapplication, an example system architecture is described below forimplementing example embodiments and features of the present disclosure.

System Architecture

Methods, systems, apparatuses, and computer program products of thepresent disclosure may be embodied by any of a variety of devices. Forexample, the method, system, apparatus, and computer program product ofan example embodiment may be embodied by one or more networked devices,such as one or more servers, remote servers, cloud-based servers (e.g.,cloud utilities), or other network entities, and configured tocommunicate with one or more devices, such as one or more serverdevices, client devices, database server devices, remote server devices,other suitable devices, or a combination thereof.

In some instances, the method, system, apparatus, and computer programproduct of an example embodiment may be embodied by one or more quantumcommunications circuitries, such as one or more quantum particleencoders, quantum particle decoders, laser devices, quantum lines,quantum particle storage devices, other suitable quantum communicationsdevices or components, or a combination thereof.

Example embodiments of the client devices include any of a variety ofstationary or mobile computing devices, such as a mobile telephone,smartphone, smartwatch, smart speaker, portable digital assistant (PDA),tablet computer, laptop computer, desktop computer, kiosk computer,automated teller machine (ATM), point of sale (PoS) device, electronicworkstation, any other suitable computing device, or any combination ofthe aforementioned devices.

FIG. 1 illustrates a system diagram of a set of devices that may beinvolved in some example embodiments described herein. In this regard,FIG. 1 discloses an example environment 100 within which embodiments ofthe present disclosure may operate to provide PQC and monitoring(including, but not limited to, QC detection, data leakage detection,data tampering detection, and identification of changes in envelopeddata structures). As illustrated, a PQC system 102 may be connected toone or more PQC server devices 104 in communication with one or more PQCdatabases 106. The PQC system 102 may be connected to one or more serverdevices 110A-110N, one or more client devices 112A-112N, one or moredatabase server devices 114, and one or more remote server devices 116through one or more communications networks 108. One or morecommunications networks 108 may include any suitable network orcombination of networks, such as a virtual network, the Internet, alocal area network (LAN), a Wi-Fi network, a Worldwide Interoperabilityfor Microwave Access (WiMAX) network, a home network, a cellularnetwork, a near field communications (NFC) network, other types ofnetworks, or a combination thereof. In some embodiments, the PQC system102 may be configured to provide PQC and monitor changes therein asdescribed in further detail below.

The PQC system 102 may be embodied as one or more specializedcircuitries, computers, or computing systems and may comprise one ormore PQC server devices 104 and one or more PQC databases 106. The oneor more PQC server devices 104 may be embodied as one or more servers,remote servers, cloud-based servers (e.g., cloud utilities), processors,any other suitable server devices, or any combination thereof. The oneor more PQC server devices 104 may be configured to receive, process,generate, and transmit data, signals, and electronic information tofacilitate the operations of the PQC system 102. The one or more PQCdatabases 106 may be embodied as one or more data storage devices, suchas Network Attached Storage (NAS) devices or separate databases orservers. The one or more PQC databases 106 may be configured to storeand provide access to data and information used by the PQC system 102 tofacilitate the operations of the PQC system 102. For example, the one ormore PQC databases 106 may store user account credentials for users ofone or more server devices 110A-110N, one or more client devices112A-112N, one or more database server devices 114, one or more remoteserver devices 116, or a combination thereof. In another example, theone or more PQC databases 106 may store data regarding devicecharacteristics for the one or more server devices 110A-110N, one ormore client devices 112A-112N, one or more database server devices 114,one or more remote server devices 116, or a combination thereof. In someembodiments, the one or more PQC server devices 104, the one or more PQCdatabases 106, or both may include or store various data and electronicinformation associated with one or more data, data attributes, dataenvelopes, enveloped data structures, policy information, policyattributes, risk profile data structures, QC detection data, QCdetection techniques (including, but not limited to, detection ofquantum computing capabilities; data leakage detection techniques; anddata tampering detection techniques), QC detection alert controlsignals, non-PQC cryptographic techniques, non-PQC cryptographicperformance information, non-PQC encryption attributes, PQCcryptographic performance information, PQC cryptographic techniques, PQCencryption attributes, symmetric cryptographic keys, asymmetriccryptographic keys, machine learning techniques, graphical userinterface (GUI) data, any other suitable data or electronic information,any links or pointers thereto, or combinations thereof. In someembodiments, the one or more PQC server devices 104, the one or more PQCdatabases 106, or both may include or store various quantum information,such as one or more quantum particles (e.g., pairs of entangled quantumparticles, one entangled quantum particle in a pair of entangled quantumparticles), quantum cryptographic keys, quantum one-time pads, any othersuitable quantum information, any links or pointers thereto, orcombinations thereof.

The one or more server devices 110A-110N may be embodied by one or morecomputing devices. In some embodiments, the one or more server devices110A-110N may be embodied as one or more servers, remote servers,cloud-based servers (e.g., cloud utilities), processors, or any othersuitable devices, or any combination thereof. In some embodiments, theone or more server devices 110A-110N may receive, process, generate, andtransmit data, signals, and electronic information to facilitate theoperations of the PQC system 102. Information received by the PQC system102 from one or more server devices 110A-110N may be provided in variousforms and via various methods. In some embodiments, the one or moreserver devices 110A-110N may include or store various data andelectronic information associated with one or more data, dataattributes, data envelopes, enveloped data structures, policyinformation, policy attributes, risk profile data structures, QCdetection data, QC detection techniques, QC detection alert controlsignals, non-PQC cryptographic techniques, non-PQC cryptographicperformance information, non-PQC encryption attributes, PQCcryptographic performance information, PQC cryptographic techniques, PQCencryption attributes, symmetric cryptographic keys, asymmetriccryptographic keys, machine learning techniques, GUI data, any othersuitable data or electronic information, any links or pointers thereto,or combinations thereof. In some embodiments, the one or more serverdevices 110A-110N may include or store various quantum information, suchas one or more quantum particles (e.g., pairs of entangled quantumparticles, one entangled quantum particle in a pair of entangled quantumparticles), quantum cryptographic keys, quantum one-time pads, any othersuitable quantum information, any links or pointers thereto, orcombinations thereof.

The one or more client devices 112A-112N may be embodied by one or morecomputing devices. Information received by the PQC system 102 from theone or more client devices 112A-112N may be provided in various formsand via various methods. For example, the one or more client devices112A-112N may be smartphones, laptop computers, netbooks, tabletcomputers, wearable devices, desktop computers, ATMs, PoS devices,electronic workstations, or the like, and the information may beprovided through various modes of data transmission provided by theseclient devices. In some embodiments, the one or more client devices112A-112N may include or store various data and electronic informationassociated with one or more users. For example, the one or more clientdevices 112A-112N may include or store user information (including, butnot limited to, user profile information), any other suitable data, orany combination thereof. In some embodiments, the one or more clientdevices 112A-112N may include or store various data and electronicinformation associated with one or more data, data attributes, dataenvelopes, enveloped data structures, policy information, policyattributes, risk profile data structures, QC detection data, QCdetection techniques, QC detection alert control signals, non-PQCcryptographic techniques, non-PQC cryptographic performance information,non-PQC encryption attributes, PQC cryptographic performanceinformation, PQC cryptographic techniques, PQC encryption attributes,symmetric cryptographic keys, asymmetric cryptographic keys, machinelearning techniques, GUI data, any other suitable data or electronicinformation, any links or pointers thereto, or combinations thereof. Insome embodiments, the one or more client devices 112A-112N may includeor store various quantum information, such as one or more quantumparticles (e.g., pairs of entangled quantum particles, one entangledquantum particle in a pair of entangled quantum particles), quantumcryptographic keys, quantum one-time pads, any other suitable quantuminformation, any links or pointers thereto, or combinations thereof.

In embodiments where a client device 112 is a mobile device, such as asmartphone or tablet, the mobile device may execute an “app” (e.g., athin-client application) to interact with the PQC system 102, one ormore server devices 110A-110N, one or more database server devices 114,one or more remote server devices 116, or a combination thereof. Suchapps are typically designed to execute on mobile devices, such astablets or smartphones. For example, an app may be provided thatexecutes on mobile device operating systems such as Apple Inc.'s iOS,Google LLC's Android®, or Microsoft Corporation's Windows®. Theseplatforms typically provide frameworks that allow apps to communicatewith one another and with particular hardware and software components ofmobile devices. For example, the mobile operating systems named aboveeach provide frameworks for interacting with camera circuitry,microphone circuitry, sensor circuitry, location services circuitry,wired and wireless network interfaces, user contacts, and otherapplications in a manner that allows for improved interactions betweenapps while also preserving the privacy and security of individual users.In some embodiments, a mobile operating system may also provide forimproved communication interfaces for interacting with external devices(e.g., server devices, client devices, database server devices, remoteserver devices). Communication with hardware and software modulesexecuting outside of the app is typically provided via APIs provided bythe mobile device operating system.

The one or more database server devices 114 may be embodied by one ormore computing devices, server devices, servers, data storage devices,databases, or a combination thereof. In some embodiments, the one ormore database server devices 114 may be embodied as one or more datastorage devices, such as one or more NAS devices, or as one or moreseparate databases or database servers. In some embodiments, the one ormore database server devices 114 may be embodied as one or more servers,remote servers, cloud-based servers (e.g., cloud utilities), processors,or any other suitable devices, or any combination thereof. In someembodiments, the one or more database server devices 114 may receive,process, generate, and transmit data, signals, and electronicinformation to facilitate the operations of the PQC system 102.Information received by the PQC system 102 from one or more databaseserver devices 114 may be provided in various forms and via variousmethods. It will be understood, however, that in some embodiments, theone or more database server devices 114 need not themselves be databasesor database servers but may be peripheral devices communicativelycoupled to databases or database servers.

In some embodiments, the one or more database server devices 114 mayinclude or store various data and electronic information associated withone or more data, data attributes, data envelopes, enveloped datastructures, policy information, policy attributes, risk profile datastructures, QC detection data, QC detection techniques, QC detectionalert control signals, non-PQC cryptographic techniques, non-PQCcryptographic performance information, non-PQC encryption attributes,PQC cryptographic performance information, PQC cryptographic techniques,PQC encryption attributes, symmetric cryptographic keys, asymmetriccryptographic keys, machine learning techniques, GUI data, any othersuitable data or electronic information, any links or pointers thereto,or combinations thereof. In some embodiments, the one or more databaseserver devices 114 may include or store exogenous data. The exogenousdata may comprise, for example, public sentiment data structures (e.g.,a widespread data breach at a third-party system, such as a merchant; astock market crash; a geopolitical event), news articles, FDIC data,NIST data, company intranet data, technological advancements, scientificpublications, financial data (e.g., stock market data, commodity marketdata, money market data), legal data (e.g., lawsuit data, regulatorydata), any other suitable exogenous data, or any combination thereof. Insome embodiments, the one or more database server devices 114 mayinclude or store various quantum information, such as one or morequantum particles (e.g., pairs of entangled quantum particles, oneentangled quantum particle in a pair of entangled quantum particles),quantum cryptographic keys, quantum one-time pads, any other suitablequantum information, any links or pointers thereto, or combinationsthereof.

The one or more remote server devices 116 may be embodied by one or morecomputing devices, server devices, servers, data storage devices,databases, or a combination thereof. In some embodiments, the one ormore remote server devices 116 may be embodied as one or more datastorage devices, such as one or more NAS devices, or as one or moreseparate databases or database servers. In some embodiments, the one ormore remote server devices 116 may be embodied as one or more servers,remote servers, cloud-based servers (e.g., cloud utilities), processors,or any other suitable devices, or any combination thereof. In someembodiments, the one or more remote server devices 116 may receive,process, generate, and transmit data, signals, and electronicinformation to facilitate the operations of the PQC system 102.Information received by the PQC system 102 from one or more remoteserver devices 116 may be provided in various forms and via variousmethods. It will be understood, however, that in some embodiments, theone or more remote server devices 116 need not themselves be servers butmay be peripheral devices communicatively coupled to servers.

In some embodiments, the one or more remote server devices 116 mayinclude or store various data and electronic information associated withone or more data, data attributes, data envelopes, enveloped datastructures, policy information, policy attributes, risk profile datastructures, QC detection data, QC detection techniques, QC detectionalert control signals, non-PQC cryptographic techniques, non-PQCcryptographic performance information, non-PQC encryption attributes,PQC cryptographic performance information, PQC cryptographic techniques,PQC encryption attributes, symmetric cryptographic keys, asymmetriccryptographic keys, machine learning techniques, GUI data, exogenousdata, any other suitable data or electronic information, any links orpointers thereto, or combinations thereof. In some embodiments, the oneor more remote server devices 116 may include or store various quantuminformation, such as one or more quantum particles (e.g., pairs ofentangled quantum particles, one entangled quantum particle in a pair ofentangled quantum particles), quantum cryptographic keys, quantumone-time pads, any other suitable quantum information, any links orpointers thereto, or combinations thereof.

In some embodiments, the one or more server devices 110A-110N, the oneor more client devices 112A-112N, the one or more database serverdevices 114, the one or more remote server devices 116, or anycombination thereof may interact with the PQC system 102 over one ormore communications networks 108. As yet another example, the one ormore server devices 110A-110N, the one or more client devices 112A-112N,the one or more database server devices 114, the one or more remoteserver devices 116, or a combination thereof may include varioushardware or firmware designed to interface with the PQC system 102. Forexample, an example server device 110A may be a session authenticationserver modified to communicate with the PQC system 102, and anotherexample server device 110B may be a purpose-built session authenticationserver offered for the primary purpose of communicating with the PQCsystem 102. As another example, an example client device 112A may be auser's smartphone and may have an application stored thereonfacilitating communication with the PQC system 102, whereas anotherexample client device 112B may be a purpose-built device offered for theprimary purpose of communicating with the PQC system 102.

In some embodiments, the one or more server devices 110A-110N, the oneor more client devices 112A-112N, the one or more database serverdevices 114, the one or more remote server devices 116, or anycombination thereof may interact with the PQC system 102 over one ormore PQC communications channels. The PQC communications channel may be,for example, a communications channel over which data is transmitted andreceived using a PQC cryptographic technique, such as a PQC back channel(e.g., a PQC out-of-band communications channel). In some embodiments,the PQC system 102 may upgrade the application software in a serverdevice 110, client device 112, database server device 114, or remoteserver device 116 so that the upgraded application software isconfigured to recognize a PQC communications channel and allowcommunication with the PQC system 102 over the PQC communicationschannel. In some embodiments, where a server device 110, client device112, database server device 114, or remote server device 116 is anon-PQC device (e.g., a computing device that is not configured tointeract with, or capable of interacting with, the PQC system 102 over aPQC communications channel), that non-PQC device may interact with thePQC system 102 over a PQC communications channel using a PQC shim or PQCadd-on device configured to allow communication with the PQC system 102over the PQC communications channel. In one example, the PQC system 102may determine that a server device 110, client device 112, databaseserver device 114, or remote server device 116 is a non-PQC device andtransmit a PQC shim to that non-PQC device for installation (e.g.,automatic installation, manual installation) in the protocol stack ofthat device. The PQC shim may be embodied as, for example, computerprogram instructions (e.g., software, firmware). In another examplewhere the server device 110, client device 112, database server device114, or remote server device 116 is a non-PQC device, a PQC add-ondevice may be communicatively coupled to the non-PQC device. The PQCadd-on device may be embodied as, for example, a PQC peripheral devicecommunicatively coupled (e.g., via a wired communications path, wirelesscommunications path, or both) to the non-PQC device. Additionally, oralternatively, the PQC add-on device may be embodied as, for example, aPQC application specific integrated circuit (ASIC) installed within ahousing of the non-PQC device, or any other suitable device orcircuitry. In some embodiments, the PQC shim may comprise a set ofroutines with network capability and a PQC endpoint.

As a foundation for some embodiments, the PQC system may communicatewith one or more of the one or more client devices 112A-112N, the one ormore server devices 110A-110N, the one or more database server devices114, the one or more remote server devices 116, any other suitabledevice, or any combination thereof using a PQC communicationschannel-based cryptographic technique.

In one example embodiment implementing a PQC communicationschannel-based cryptographic technique, the PQC system 102 may transmit afirst portion of an electronic communication (e.g., overhead data) overa non-PQC communications channel (e.g., a communications channel throughone or more communications networks 108) to one or more of the one ormore client devices 112A-112N, the one or more server devices 110A-110N,the one or more database server devices 114, the one or more remoteserver devices 116, any other suitable device, or any combinationthereof. The PQC system 102 may further transmit a second portion of theelectronic communication (e.g., payload data) over a PQC communicationschannel (e.g., a back channel or out-of-band communications channelthrough one or more communications networks 108) to the one or more ofthe one or more client devices 112A-112N, the one or more server devices110A-110N, the one or more database server devices 114, the one or moreremote server devices 116, any other suitable device, or any combinationthereof.

In another example embodiment implementing a PQC communicationschannel-based cryptographic technique, the PQC system 102 may transmit afirst portion of an electronic communication over a non-PQCcommunications channel to one or more of the one or more client devices112A-112N, the one or more server devices 110A-110N, the one or moredatabase server devices 114, the one or more remote server devices 116,any other suitable device, or any combination thereof. The PQC system102 may further transmit a second portion of the electroniccommunication over a PQC communications channel to one or more PQCadd-on devices, wherein each of the one or more PQC add-on devices iscommunicatively coupled to a respective client device 112, server device110, database server device 114, remote server device 116, any othersuitable device, or any combination thereof.

In yet another example embodiment implementing a PQC communicationschannel-based cryptographic technique, the PQC system may transmit afirst portion of an electronic communication over a non-PQCcommunications channel and transmit a quantum cryptographic key to aclient device over a quantum communications channel. The PQC system mayfurther authenticate a session with the client device over the non-PQCcommunications channel based on the quantum cryptographic key. Inresponse to authentication of the session with the client device, thePQC system may transmit a second portion of the electronic communicationto the client device over a PQC communications channel.

In some embodiments, the PQC system 102 may provide for receiving dataand generating a set of data attributes about the data. In someembodiments, the PQC system 102 may provide for receiving, directly orindirectly via communications network 108, the data from one or more ofthe one or more client devices 112A-112N, the one or more server devices110A-110N, the one or more database server devices 114, any othersuitable device, or any combination thereof. In some embodiments, thePQC system 102 may further provide for generating a data envelope basedon the set of data attributes. In some embodiments, the PQC system 102may further provide for generating an enveloped data structure based onthe data envelope and the data.

In some embodiments, the PQC system 102 may provide for retrievingpolicy information associated with the data. In some embodiments, thePQC system 102 may provide for retrieving, directly or indirectly viacommunications network 108, the policy information from one or more ofthe one or more client devices 112A-112N, the one or more server devices110A-110N, the one or more database server devices 114, the one or moreremote server devices 116, any other suitable device, or any combinationthereof. In some embodiments, the PQC system 102 may further provide forgenerating a set of policy attributes about the data based on the dataand the policy information. In some embodiments, the PQC system 102 mayfurther provide for generating a risk profile data structure based onthe set of policy attributes. The risk profile data structure may beindicative of a vulnerability of the data in a PQC data environment.

In some embodiments, the PQC system 102 may provide for retrieving PQCcryptographic performance information associated with a set of PQCcryptographic techniques. In some embodiments, the PQC system 102 mayprovide for retrieving, directly or indirectly via communicationsnetwork 108, the policy information from one or more of the one or morePQC server devices 104, the one or more PQC databases 106, the one ormore database server devices 114, the one or more remote server devices116, any other suitable device, or any combination thereof. In someembodiments, the PQC system 102 may provide for generating a PQCcryptographic technique for encrypting the data based on the set of PQCencryption attributes, and encrypt the data using the generated PQCcryptographic technique.

In some embodiments, the PQC cryptographic performance information maycomprise a set of PQC cryptographic performance attributes for each PQCcryptographic technique in the set of PQC cryptographic techniques. Insome embodiments, the PQC system 102 may further provide for generatinga set of PQC encryption attributes for encrypting the data based on theset of data attributes, the risk profile data structure, and the PQCcryptographic performance information. In some embodiments, the PQCcryptographic performance information comprises information indicativeof the algorithm and implementation scale for each PQC cryptographictechnique in the set of PQC cryptographic techniques; the efficiency,performance, and deterministic operation of each PQC cryptographictechnique in the set of PQC cryptographic techniques; the confidencescore (e.g., based on cryptanalysis) for each PQC cryptographictechnique in the set of PQC cryptographic techniques; the usability andinteroperability of each PQC cryptographic technique in the set of PQCcryptographic techniques; any other suitable data or electronicinformation; or any combination thereof.

In some embodiments, the PQC system 102 may provide for generating thePQC cryptographic performance information. In some embodiments, the PQCsystem 102 may provide for storing the PQC cryptographic performanceinformation in a PQC cryptographic performance information storagedevice. The PQC cryptographic performance information storage device maybe, for example, one or more of the one or more PQC databases 106, thePQC server devices 104, the one or more client devices 112, the one ormore server devices 110, the one or more database server devices 114,the one or more remote server devices 116, or a combination thereof.

In some embodiments, the PQC system 102 may further provide forencrypting the data based on the set of PQC encryption attributes. Insome embodiments, the PQC system 102 may provide for storing theencrypted data in a data storage device. The data storage device may be,for example, one or more of the one or more database server devices 114,the one or more PQC databases 106, the one or more client devices 112,the one or more server devices 110, or a combination thereof.

In some embodiments, the PQC system 102 may provide adaptive PQC bymonitoring an enveloped data structure to identify a change in theenveloped data structure and, in response, determine whether to generatenew PQC encryption attributes for re-encrypting or double encryptingdata contained in the enveloped data structure. For example, theenveloped data structure may comprise a data envelope and data. The dataenvelope may comprise a set of data attributes about the data and a riskprofile data structure indicative of a vulnerability of the data in aPQC data environment. The data may have been encrypted based on a firstset of PQC encryption attributes. In some embodiments, the PQC system102 may further provide for generating an electronic indication of achange in the enveloped data structure. In some embodiments, the PQCsystem 102 may further provide for, in response to generating theelectronic indication of the change in the enveloped data structure,retrieving PQC cryptographic performance information associated with aset of PQC cryptographic techniques. The PQC cryptographic performanceinformation may comprise a set of PQC cryptographic performanceattributes for each PQC cryptographic technique in the set of PQCcryptographic techniques. In some embodiments, the PQC system 102 mayfurther provide for generating a second set of PQC encryption attributesfor encrypting the data based on the set of data attributes, the riskprofile data structure, the change in the enveloped data structure, andthe PQC cryptographic performance information.

In some embodiments, the PQC system 102 may further provide forre-encrypting or double encrypting the data based on the second set ofPQC encryption attributes. In some embodiments, the PQC system 102 mayprovide for storing the re-encrypted or double encrypted data in a datastorage device. The data storage device may be, for example, one or moreof the one or more database server devices 114, the one or more PQCdatabases 106, the one or more client devices 112, the one or moreserver devices 110, or a combination thereof.

In some embodiments, the PQC system 102 may provide for generating QCdetection data and encrypting the QC detection data based on acryptographic technique. In one example, the PQC system 102 may providefor generating a pair of asymmetric cryptographic keys comprising apublic cryptographic key and a private cryptographic key, encrypting theQC detection data based on the pair of asymmetric cryptographic keys,and destroying the private cryptographic key. In some embodiments, thePQC system 102 may further provide for monitoring a set of dataenvironments for electronic information related to the encrypted QCdetection data. For example, the PQC system 102 may provide formonitoring internal and external data environments implemented by one ormore of the one or more client devices 112A-112N, the one or more serverdevices 110A-110N, the one or more database server devices 114, anyother suitable device, or any combination thereof. In some embodiments,the PQC system 102 may be further configured to generate a QC detectionalert control signal in response to detection of the electronicinformation related to the encrypted QC detection data. In someembodiments, the PQC system 102 may be further configured to generate aleakage alert control signal, a tampering alert control signal, anyother suitable control signal, or any combination thereof.

In some embodiments, the PQC system 102, or a QC detection systemcomprised by or in communication with the PQC system 102, may providefor detecting the realization of a quantum computer based on various QCdetection techniques. For example, the PQC system 102 may provide for adigital signature-based QC detection technique configured to detect afraudulent document signed using a destroyed RSA private key. In anotherexample, the PQC system 102 may provide for an encryption-based QCdetection technique configured to detect disclosed information encryptedusing a random AES key encrypted using a destroyed RSA private key(e.g., protecting cleartext against disclosure for verification). Inanother example, the PQC system 102 may provide for a code-sign based QCdetection technique configured to detect code-sign malware using adestroyed RSA private key. In another example, the PQC system 102 mayprovide for a certificate-based QC detection technique configured todetect a fraudulent certificate signed by an issuer certificateauthority using a destroyed RSA private key (e.g., using a fictitiousemail certificate or legal sign certificate as a honeypot). In anotherexample, the PQC system 102 may provide for a tamper seal-based QCdetection technique configured to detect a fraudulent PDF with anembedded digital signed object.

In some embodiments, the PQC system 102 may further provide forreceiving a QC detection alert control signal, a leakage alert controlsignal, or a tampering alert control signal and, in response, generatingan electronic indication of a change in the enveloped data structurebased on the QC detection alert control signal, the leakage alertcontrol signal, or the tampering alert control signal. In someembodiments, the PQC system 102 may further provide for, in response togenerating the electronic indication of the change in the enveloped datastructure, retrieving PQC cryptographic performance informationassociated with a set of PQC cryptographic techniques. The PQCcryptographic performance information may comprise a set of PQCcryptographic performance attributes for each PQC cryptographictechnique in the set of PQC cryptographic techniques. In someembodiments, the PQC system 102 may further provide for generating asecond set of encryption attributes (e.g., PQC encryption attributes)for encrypting the data based on the set of data attributes, the riskprofile data structure, the change in the enveloped data structure, andthe PQC cryptographic performance information.

In some embodiments, the PQC system 102 may further provide forgenerating a portfolio view (e.g., GUI) of existing businessapplications for modeling what the impact of applying a specific PQCcryptographic technique would be across an entire portfolio. In oneillustrative example, if the PQC system 102 determines that it must usePQC cryptographic technique Z to generate a symmetric key to encryptdata, the PQC system 102 may be further configured to generate portfolioGUI data and transmit that portfolio GUI data to a client device 112 toshow users which applications would be suitable for implementing PQCcryptographic technique Z (e.g., the additional encryption overheadwould not exceed application transaction time limits), whichapplications would be borderline, and which applications would be “inthe red” and would exceed transaction time limits.

Example Implementing Apparatuses

The PQC system 102 described with reference to FIG. 1 may be embodied byone or more computing systems, such as apparatus 200 shown in FIG. 2A,apparatus 280 shown in FIG. 2B, and apparatus 290 shown in FIG. 2C. Insome embodiments, apparatus 200 shown in FIG. 2A may represent anexample PQC system 102, a PQC server device 104, a PQC database, or acombination thereof. In some embodiments, apparatus 280 shown in FIG. 2Bmay represent an example server device 110, client device 112, databaseserver device 114, remote server device 116, any other suitable device,or a combination thereof. In some embodiments, apparatus 290 shown inFIG. 2B may represent an example PQC add-on device configured to becommunicatively coupled to a server device 110, client device 112,database server device 114, remote server device 116, any other suitabledevice, or a combination thereof.

As illustrated in FIG. 2A, the apparatus 200 may include one or more ofprocessing circuitry 202, memory 204, input-output circuitry 206, PQCcallback circuitry 207, communications circuitry 208 (including, but notlimited to, classical communications circuitry 210 and quantumcommunications circuitry 212), data attribute generation circuitry 214,data envelope generation circuitry 216, data structure generationcircuitry 218, data monitoring circuitry 220 (including, but not limitedto, data access monitoring circuitry 222 and data zone monitoringcircuitry 224), policy attribute generation circuitry 226, risk profilegeneration circuitry 228, vulnerability scan circuitry 230,vulnerability score generation circuitry 232, compliance scoregeneration circuitry 234, cryptographic performance circuitry 236(including, but not limited to, non-PQC cryptographic performancecircuitry 238 and PQC cryptographic performance circuitry 240),cryptographic attribute generation circuitry 242 (including, but notlimited to, non-PQC cryptographic attribute generation circuitry 244 andPQC cryptographic attribute generation circuitry 246), cryptographiccircuitry 248 (including, but not limited to, non-PQC cryptographiccircuitry 250 and PQC cryptographic circuitry 252), machine learningcircuitry 254, data storage circuitry 256, user interface (UI) circuitry258, any other suitable circuitry, or any combination thereof. Theapparatus 200 may be configured to execute the operations describedabove with respect to FIG. 1 and below with respect to FIGS. 3-8.

In some embodiments, the processing circuitry 202 (and/or co-processoror any other processing circuitry assisting or otherwise associated withthe processor) may be in communication with the memory 204 via a bus forpassing information among components of the apparatus 200. The memory204 may be non-transitory and may include, for example, one or morevolatile and/or non-volatile memories. For example, the memory may be anelectronic storage device (e.g., a computer readable storage medium).The memory 204 may be configured to store information, data, datastructures, content, control signals, applications, instructions, or thelike, for enabling the apparatus to carry out various functions inaccordance with example embodiments of the present disclosure. In someinstances, the memory 204 may be configured to store data, datastructures, data elements, and electronic information associated withone or more data (e.g., unencrypted data, encrypted data, decrypteddata, re-encrypted data, double encrypted data, data access controlinformation, bitstreams of data, QC detection data, links or pointersthereto), data attributes, data envelopes, enveloped data structures,policy information, policy attributes, risk profile data structures, QCdetection techniques (including, but not limited to, detection ofquantum computing capabilities; data leakage detection techniques; anddata tampering detection techniques), control signals (e.g., QCdetection alert control signals), non-PQC cryptographic techniques,non-PQC cryptographic performance information, non-PQC encryptionattributes, PQC cryptographic performance information, PQC cryptographictechniques, PQC encryption attributes, symmetric cryptographic keys,asymmetric cryptographic keys, any other suitable data or electronicinformation, or combinations thereof. It will be understood that thememory 204 may be configured to store any data, data structures,electronic information, requests, control signals, embodiments,examples, figures, techniques, processes, operations, methods, systems,apparatuses, or computer program products described herein, or anycombination thereof.

The processing circuitry 202 may be embodied in a number of differentways and may, for example, include one or more processing devicesconfigured to perform independently. Additionally, or alternatively, theprocessing circuitry 202 may include one or more processors configuredin tandem via a bus to enable independent execution of instructions,pipelining, multithreading, or a combination thereof. The use of theterm “processing circuitry” may be understood to include a single coreprocessor, a multi-core processor, multiple processors internal to theapparatus, remote or “cloud” processors, or a combination thereof.

In an example embodiment, the processing circuitry 202 may be configuredto execute instructions stored in the memory 204 or otherwise accessibleto the processor. Alternatively, or additionally, the processingcircuitry 202 may be configured to execute hard-coded functionality. Assuch, whether configured by hardware or software methods, or by acombination of hardware with software, the processor may represent anentity (e.g., physically embodied in circuitry) capable of performingoperations according to an embodiment of the present disclosure whileconfigured accordingly. As another example, when the processor isembodied as an executor of software instructions, the instructions mayspecifically configure the processor to perform the functionalities andoperations described herein when the instructions are executed.

In some embodiments, the apparatus 200 may include input-outputcircuitry 206 that may, in turn, be in communication with processingcircuitry 202 to provide output to the user and, in some embodiments, toreceive an indication of a user input such as a command provided by auser. The input-output circuitry 206 may comprise a user interface(e.g., a user interface generated by user interface circuitry includedin the apparatus 200) comprising a display that may include a web userinterface, a mobile application, a client device, a display device, adisplay screen, or any other suitable hardware or software. In someembodiments, the input-output circuitry 206 may also include a keyboard,a mouse, a joystick, a touch screen, touch areas, soft keys, amicrophone, a speaker, or other input-output mechanisms. The processingcircuitry 202, the input-output circuitry 206 (which may utilize theprocessing circuitry 202), or both may be configured to control one ormore functions of one or more user interface elements through computerprogram instructions (e.g., software, firmware) stored on a memory(e.g., memory 204). Input-output circuitry 206 is optional and, in someembodiments, the apparatus 200 may not include input-output circuitry.For example, where the apparatus 200 does not interact directly with theuser, the apparatus 200 may be configured to generate (e.g., by UIcircuitry 258) user interface data (e.g., data attribute GUI data, riskprofile GUI data, PQC optimization GUI data, data monitoring GUI data)for display by one or more other devices with which one or more usersdirectly interact and transmit the generated user interface data to oneor more of those devices.

In some embodiments, the apparatus 200 may include PQC callbackcircuitry 207 that includes hardware components designed or configuredto provide for communication with: the PQC cryptographic circuitry(e.g., PQC cryptographic circuitry 252 shown in FIG. 2B) of a clientdevice (e.g., apparatus 280 shown in FIG. 2B, wherein the apparatus 280does not include the PQC shim circuitry 260); a PQC shim (e.g., PQC shimcircuitry 260 shown in FIG. 2B) installed in a network layer of a clientdevice (e.g., apparatus 280 shown in FIG. 2B, wherein the apparatus 280includes the PQC shim circuitry 260, and wherein the PQC shim circuitry260 comprises the PQC cryptographic circuitry 252); a PQC add-on device(e.g., the apparatus 290 shown in FIG. 2C) communicatively coupled to aclient device (e.g., apparatus 280 shown in FIG. 2B, wherein theapparatus 280 does not include the PQC cryptographic circuitry 252 orthe PQC shim circuitry 260); any other suitable circuitry or device; orany combination thereof. For example, PQC callback circuitry 207 may beconfigured to provide PQC communications channel-based cryptographictechniques, such as the transmission and receipt of sensitive portions(e.g., payloads) of electronic communications to a PQC shim or a PQCadd-on device over one or more PQC communications channels.

In some embodiments, the PQC callback circuitry 207 may be configured toestablish a non-PQC communications channel based on one or more non-PQCcryptographic algorithms (e.g., as provided by non-PQC cryptographiccircuitry 250). In some embodiments, the PQC callback circuitry 207 maybe configured to establish a PQC communications channel based on one ormore PQC cryptographic algorithms (e.g., as provided by PQCcryptographic circuitry 252). In some embodiments, the PQC callbackcircuitry 207 may be configured to establish a hybrid PQC communicationschannel based on one or more hybrid PQC cryptographic algorithms (e.g.,as provided by cryptographic circuitry 248, such as provided by acombination of non-PQC cryptographic circuitry 250 and PQC cryptographiccircuitry 252).

In one illustrative example, the PQC callback circuitry 207 may beconfigured to establish a PQC communications channel using a PQCcryptographic algorithm. The cryptographic circuitry 248 may be furtherconfigured to generate a secret key (e.g., an AES symmetriccryptographic key). Thereafter, the PQC callback circuitry 207 maytransmit the secret key to a remote device (e.g., apparatus 280,apparatus 290) over the PQC communications channel for use in thesubsequent exchange of encrypted communications.

In some embodiments, the PQC callback circuitry 207 may be configured togenerate (e.g., dynamically generate) the PQC communications channelbased on a set of data attributes about the electronic communication, arisk profile data structure indicative of a vulnerability of theelectronic communication in a PQC data environment, and PQC performanceinformation associated with a set of PQC cryptographic techniques,wherein the PQC performance information comprises a set of PQCperformance attributes for each PQC cryptographic technique in the setof PQC cryptographic techniques. In some embodiments, the PQC callbackcircuitry 207 may be configured to generate the PQC communicationschannel based on a machine learning technique, such as a machinelearning technique provided or performed by the machine learningcircuitry 254.

The communications circuitry 208 may be any device or circuitry embodiedin either hardware or a combination of hardware and software that isconfigured to receive and/or transmit classical data, quantuminformation, or both from or to a network and/or any other device,circuitry, or module in communication with the apparatus 200. In thisregard, the communications circuitry 208 may include, for example,classical communications circuitry 210 and quantum communicationscircuitry 212.

The classical communications circuitry 210 may be any device orcircuitry embodied in either hardware or a combination of hardware andsoftware that is configured to receive and/or transmit data from or to anetwork and/or any other device, circuitry, or module in communicationwith the apparatus 200. In this regard, the classical communicationscircuitry 210 may include, for example, a network interface for enablingcommunications with a wired or wireless communications network. Forexample, the classical communications circuitry 210 may include one ormore network interface cards, antennae, buses, switches, routers,modems, and supporting hardware and/or software, or any other devicesuitable for enabling communications via a network. In some embodiments,the communication interface may include the circuitry for interactingwith the antenna(s) to cause transmission of signals via the antenna(s)or to handle receipt of signals received via the antenna(s). Thesesignals may be transmitted by the apparatus 200 using any of a number ofwireless personal area network (PAN) technologies, such as Bluetooth®v1.0 through v5.0, Bluetooth Low Energy (BLE), infrared wireless (e.g.,IrDA), ultra-wideband (UWB), induction wireless transmission, or anyother suitable technologies. In addition, it should be understood thatthese signals may be transmitted using Wi-Fi, NFC, WiMAX or otherproximity-based communications protocols.

The quantum communications circuitry 212 may be any device or circuitryembodied in either hardware or a combination of hardware and softwarethat is configured to receive and/or transmit quantum particles, such asphotons, electrons, or both from or to any other device, circuitry, ormodule in communication with the apparatus 200. In this regard, thequantum communications circuitry 212 may include, for example, opticalcomponents such as an optical communications interface for enablingoptical communications over a quantum line. In some embodiments, thequantum communications circuitry 212 may include encoding circuitry(e.g. an on-chip encoder) to generate a set of entangled quantumparticles (e.g., qubits, qutrits, qudits) and decoding circuitry (e.g.,an on-chip decoder) to receive (e.g., directly or indirectly, such asvia switching circuitry), store, and measure a set of entangled quantumparticles. In some embodiments, the quantum communications circuitry 212may further include quantum basis determination circuitry configured todetermine the quantum bases, or sets of quantum bases, for encoding anddecoding of a given set of quantum particles. In some embodiments, thequantum communications circuitry 212 may include or be communicativelycoupled to one or more quantum storage devices configured to storevarious quantum information, such as one or more quantum particles(e.g., pairs of entangled quantum particles, one entangled quantumparticle in a pair of entangled quantum particles), quantumcryptographic keys, quantum one-time pads, any other suitable quantuminformation, any links or pointers thereto, and combinations thereof.

In some embodiments, the first portion of the electronic communicationmay comprise a PQC indicator data structure that identifies the PQCcommunications channel and indicates that the second portion of theelectronic communication is to be transmitted over the PQCcommunications channel. In some embodiments, the PQC indicator datastructure may comprise a link to a PQC shim configured to allowcommunication with the PQC callback circuitry 207 over the PQCcommunications channel. For example, the PQC indicator data structuremay comprise a PQC shim automatic installation control signal indicativeof an electronic instruction for the client device (e.g., apparatus 280shown in FIG. 2B) to automatically install the PQC shim based on thelink. In another example, the PQC indicator data structure may comprisea PQC shim manual installation control signal indicative of anelectronic instruction for the client device to manually install the PQCshim based on the link. In still another example, the first portion ofthe electronic communication may comprise a PQC smart contractcomprising the PQC indicator data structure. Once installed on theclient device, the PQC shim may be implemented as PQC shim circuitry 260shown in FIG. 2B.

In some embodiments, the communications circuitry 208 may be configuredto receive, retrieve, or obtain data. In some embodiments, the data maycomprise data access control information, a link or pointer to the data(e.g., a link to a credit card number), a bitstream, a binary largeobject (BLOB), any other suitable data, or any combination thereof. Insome embodiments, the data may have been encrypted based on a set ofencryption attributes, such as a set of non-PQC encryption attributes, aset of PQC encryption attributes, or both (e.g., double encryption wherethe data has been encrypted based on a set of non-PQC encryptionattributes and then double encrypted based on a set of PQC encryptionattributes). In some embodiments, the communications circuitry 208 maybe configured to receive, retrieve, or obtain the data from a datastorage device, such as memory 204, one or more of the one or more PQCdatabases 106, the one or more database server devices 114 (including,but not limited to, one or more data storage devices communicativelycoupled, either directly or indirectly, to the one or more databaseserver devices 114), the one or more remote server devices 116, the oneor more server devices 110A-110N, the one or more client devices112A-112N, any other suitable device or circuitry, or a combinationthereof.

In some embodiments, the communications circuitry 208 may be configuredto receive, retrieve, or obtain a set of data attributes about the data.In some embodiments, the communications circuitry 208 may be configuredto receive, retrieve, or obtain the set of data attributes from anothercircuitry, such as processing circuitry 202, data attribute generationcircuitry 214, any other suitable circuitry, or a combination thereof.In some embodiments, the communications circuitry 208 may be configuredto receive, retrieve, or obtain the set of data attributes from a datastorage device, such as memory 204, one or more of the one or more PQCdatabases 106, the one or more database server devices 114 (including,but not limited to, one or more data storage devices communicativelycoupled, either directly or indirectly, to the one or more databaseserver devices 114), the one or more remote server devices 116, the oneor more server devices 110A-110N, the one or more client devices112A-112N, any other suitable device or circuitry, or a combinationthereof. In some embodiments, where the data is included in an envelopeddata structure comprising the data and a data envelope that comprisesthe set of data attributes, the communications circuitry 208 may beconfigured to receive, retrieve, or obtain the set of data attributes byextracting the set of data attributes from the data envelope.

In some embodiments, the communications circuitry 208 may be configuredto receive, retrieve, or obtain policy information associated with thedata. In some embodiments, the communications circuitry 208 may beconfigured to receive, retrieve, or obtain the policy information fromanother circuitry, such as processing circuitry 202, policy attributegeneration circuitry 226, any other suitable circuitry, or a combinationthereof. In some embodiments, the communications circuitry 208 may beconfigured to receive, retrieve, or obtain the policy information from adata storage device, such as memory 204, one or more of the one or morePQC databases 106, the one or more database server devices 114(including, but not limited to, one or more data storage devicescommunicatively coupled, either directly or indirectly, to the one ormore database server devices 114), the one or more remote server devices116, the one or more server devices 110A-110N, the one or more clientdevices 112A-112N, any other suitable device or circuitry, or acombination thereof.

In some embodiments, the communications circuitry 208 may be configuredto receive, retrieve, or obtain a risk profile data structure indicativeof a vulnerability of the data in a PQC data environment. In someembodiments, the communications circuitry 208 may be configured toreceive, retrieve, or obtain the risk profile data structure fromanother circuitry, such as processing circuitry 202, risk profilegeneration circuitry 228, any other suitable circuitry, or a combinationthereof. In some embodiments, the communications circuitry 208 may beconfigured to receive, retrieve, or obtain the risk profile datastructure from a data storage device, such as memory 204, one or more ofthe one or more PQC databases 106, the one or more database serverdevices 114 (including, but not limited to, one or more data storagedevices communicatively coupled, either directly or indirectly, to theone or more database server devices 114), the one or more remote serverdevices 116, the one or more server devices 110A-110N, the one or moreclient devices 112A-112N, any other suitable device or circuitry, or acombination thereof. In some embodiments, where the data is included inan enveloped data structure comprising the data and a data envelope thatcomprises the risk profile data structure, the communications circuitry208 may be configured to receive, retrieve, or obtain the risk profiledata structure by extracting the risk profile data structure from thedata envelope.

In some embodiments, the communications circuitry 208 may be configuredto receive, retrieve, or obtain PQC cryptographic performanceinformation associated with a set of PQC cryptographic techniques. Insome embodiments, the communications circuitry 208 may be configured toreceive, retrieve, or obtain the PQC cryptographic performanceinformation from another circuitry, such as processing circuitry 202,PQC cryptographic performance circuitry 240, any other suitablecircuitry, or a combination thereof. In some embodiments, thecommunications circuitry 208 may be configured to receive, retrieve, orobtain the PQC cryptographic performance information from a data storagedevice, such as memory 204, one or more of the one or more PQC databases106, the one or more database server devices 114 (including, but notlimited to, one or more data storage devices communicatively coupled,either directly or indirectly, to the one or more database serverdevices 114), the one or more remote server devices 116, the one or moreserver devices 110A-110N, the one or more client devices 112A-112N, anyother suitable device or circuitry, or a combination thereof.

The data attribute generation circuitry 214 includes hardware componentsdesigned or configured to request, receive, process, generate, andtransmit data, data structures, control signals, and electronicinformation for use in PQC. In some embodiments, the data attributegeneration circuitry 214 may be configured to generate a set of dataattributes about data, such as the data received by the communicationscircuitry 208, based on the data. In some embodiments, the dataattribute generation circuitry 214 may be configured to generate the setof data attributes about the data based on the data itself, overheaddata (e.g., protocol overhead, header, metadata) associated with thedata, any other suitable data or electronic information, or anycombination thereof. In some embodiments, the data attribute generationcircuitry 214 may be configured to generate the set of data attributesabout the data based on a machine learning technique, such as a machinelearning technique provided or performed by the machine learningcircuitry 254.

In some embodiments, the set of data attributes about the data maycomprise a data lineage data attribute indicative of a data lineage ofthe data. For example, the data attribute generation circuitry 214 maybe configured to generate a data lineage data attribute indicative of adata lineage of the data, wherein the set of data attributes comprisesthe data lineage data attribute.

In some embodiments, the set of data attributes about the data maycomprise a cryptographic data attribute indicative of a cryptographictechnique used to encrypt the data. In some instances, the dataattribute generation circuitry 214 may be configured to generate,without user interactivity, the cryptographic data attribute based on anautomated analysis of a bitstream of the data. For example, the data maycomprise a bitstream, and the data attribute generation circuitry 214may be configured to generate, based on an automated analysis of thebitstream and without user interactivity, a cryptographic data attributeindicative of a cryptographic technique used to encrypt the data,wherein the set of data attributes comprises the cryptographic dataattribute.

In some embodiments, the set of data attributes about the data maycomprise a cryptographic spawn log indicative of a set of cryptographictechniques used to encrypt the data. For example, the data attributegeneration circuitry 214 may be configured to generate a cryptographicspawn log comprising a set of timestamps and information indicative ofsets of PQC encryption attributes used to encrypt the data over a periodof time (e.g., lifetime of the data; the last three years, or any othersuitable period or duration of time), wherein each timestamp in the setof timestamps corresponds to a set of PQC encryption attributes used toencrypt the data at the time associated with the timestamp. In anotherexample, the data attribute generation circuitry 214 may be configuredto generate a cryptographic spawn log comprising a set of encryptionidentification numbers and information indicative of sets of PQCencryption attributes used to encrypt the data over an amount ofencryptions (e.g., all encryptions; the last five encryptions, or anyother suitable amount of encryptions), wherein each encryptionidentification number in the set of encryption identification numberscorresponds to a set of PQC encryption attributes used to encrypt thedata at the time associated with the encryption identification number.In some embodiments, the data attribute generation circuitry 214 may beconfigured to generate a cryptographic spawn log comprising a timestampand information indicative of the set of PQC encryption attributes usedto encrypt the data. In some embodiments, the data attribute generationcircuitry 214 may be configured to generate an updated cryptographicspawn log comprising a second timestamp and information indicative of asecond set of PQC encryption attributes used to encrypt the data.

In some embodiments, the set of data attributes about the data maycomprise a data access log indicative of a set of data activitymonitoring information (e.g., database activity monitoring information,access credentials, user identification information, machineidentification information) associated with electronic access to thedata. For example, the data attribute generation circuitry 214 may beconfigured to generate a data access log comprising a set of timestampsand information indicative of sets of data activity monitoringinformation the data over a period of time (e.g., lifetime of the data;the last three years, or any other suitable period or duration of time),wherein each timestamp in the set of timestamps corresponds to a set ofPQC encryption attributes used to encrypt the data at the timeassociated with the timestamp. In some embodiments, the set of dataattributes about the data may comprise a determination that the data hasbeen accessed. For example, the data attribute generation circuitry 214may be configured to receive the determination that the data has beenaccessed from the data access monitoring circuitry 222.

In some embodiments, the set of data attributes about the data maycomprise a data zone data attribute indicative of a data zone associatedwith the data. For example, the data attribute generation circuitry 214may be configured to generate a data zone data attribute indicative of adata zone associated with the data, wherein the set of data attributescomprises the data zone data attribute. In some embodiments, the set ofdata attributes about the data may comprise a determination that thedata has transitioned from a first data zone to a second data zone. Forexample, the data attribute generation circuitry 214 may be configuredto receive the determination that the data has transitioned from a firstdata zone to a second data zone from the data zone monitoring circuitry224.

The data envelope generation circuitry 216 includes hardware componentsdesigned or configured to request, receive, process, generate, andtransmit data, data structures, control signals, and electronicinformation for use in PQC. In some embodiments, the data envelopegeneration circuitry 216 may be configured to generate a data envelopebased on the set of data attributes. In some embodiments, the dataenvelope generation circuitry 216 may be configured to generate the dataenvelope based on the set of data attributes. In some embodiments, thedata envelope may comprise the set of data attributes. In someembodiments, the data envelope generation circuitry 216 may beconfigured to generate the data envelope based on the set of dataattributes, a risk profile data structure, any other suitable data, orany combination thereof. In some embodiments, the data envelope maycomprise the set of data attributes, a risk profile data structure, anyother suitable data, or any combination thereof. In some embodiments,each piece of data may have a data envelope, wherein the data envelopecomprises one or more attributes about the data. In some embodiments,the data and its envelope may be referred to as a “data BLOB.” In someinstances, the data envelope will keep track of who accessed the data,such as who took an encrypted snapshot of the data and when thatencrypted snapshot was taken.

The data structure generation circuitry 218 includes hardware componentsdesigned or configured to request, receive, process, generate, andtransmit data, data structures, control signals, and electronicinformation for use in PQC. In some embodiments, the data structuregeneration circuitry 218 may be configured to generate an enveloped datastructure based on the data envelope and the data. In some embodiments,the enveloped data structure comprises the data envelope and the data.In some embodiments, the enveloped data structure comprises the dataenvelope (e.g., set of data attributes, risk profile data structure, anyother suitable data, or any combination thereof) and the data (e.g.,data access control information, link or pointer to the data, bitstream,BLOB, any other suitable data, or any combination thereof). For example,the enveloped data structure may comprise the data enveloped by the dataenvelope.

The data monitoring circuitry 220 includes hardware components designedor configured to request, receive, process, generate, and transmit data,data structures, control signals, and electronic information for use inPQC. In some embodiments, the data monitoring circuitry 220 may beconfigured to monitor data, enveloped data structures, any othersuitable data or electronic information, or any combination thereof. Inthis regard, the data monitoring circuitry 220 may include, for example,data access monitoring circuitry 222 and data zone monitoring circuitry224.

In some embodiments, the data monitoring circuitry 220 may be configuredto monitor an enveloped data structure and identify changes in theenveloped data structure. In some embodiments, the enveloped datastructure may comprise a data envelope and data. In some embodiments,the data envelope may comprise a set of data attributes about the dataand a risk profile data structure indicative of a vulnerability of thedata in a PQC data environment. In some embodiments, the data has beenencrypted based on a set of non-PQC encryption attributes or a set ofPQC encryption attributes. For example, the data monitoring circuitry220 may be configured to generate an electronic indication of the changein the enveloped data structure, such as a control signal, metadata, orflag indicative of the change. In some embodiments, the data monitoringcircuitry 220 may be configured to automatically monitor the envelopeddata structure in real-time and without user interactivity;automatically identify the change in the enveloped data structure inreal-time and without user interactivity; and generate the electronicindication of the change in the enveloped data structure in real-timeand without user interactivity.

In some embodiments, the change in the enveloped data structure may be achange in the risk profile data structure, such as a change in a valueof the data, a change in a longevity of the data, a change in acryptostrength of the data, a change in a result of a vulnerability scanof the data, a change in a vulnerability score value (e.g., any valueassociated with a vulnerability score data structure comprising avulnerability score range comprising a minimum vulnerability scorevalue, a maximum vulnerability score value, a median vulnerability scorevalue, a mean vulnerability score value, a first quartile vulnerabilityscore value, a third quartile vulnerability score value, aninterquartile vulnerability score range between the first quartilevulnerability score value and the third quartile vulnerability scorevalue, any other suitable value, metric, or range, or any combinationthereof) indicative of a percentage of vulnerability of the data in thePQC data environment, a change in a compliance score value indicative ofa percentage of compliance of the data to a set of compliancerequirements, a change in an approximate time to a quantum computingthreat (e.g., changes in collapse time, changes in vulnerabilities toexisting algorithms, receipt of a QC detection alert control signal), achange in exogenous data associated with the data, wherein the exogenousdata comprises a public sentiment data structure (e.g., a widespreaddata breach at a third-party system, such as a merchant; a stock marketcrash; a geopolitical event), a change in any other suitable data, datastructure, or data element, or any combination thereof. In someembodiments, the change in the enveloped data structure may be adetermination that the data has been accessed and by whom (e.g., user,entity, location). In some embodiments, the change in the enveloped datastructure may be a determination that the data has transitioned to adifferent data zone (e.g., from a first data zone to a second datazone).

In some embodiments, the data monitoring circuitry 220 may be configuredto monitor a set of data environments for electronic information relatedto the encrypted QC detection data. For example, the data monitoringcircuitry 220 may be configured to monitor a set of internal dataenvironments (e.g., internal information systems, internal datanetworks, internal data storage devices) and, in some instances, flaguses of the QC detection data, the private cryptographic key used toencrypt the QC detection data, or any other suitable data that made itsway into the internal data environment. In another example, the datamonitoring circuitry 220 may be configured to monitor a set of externaldata environments (e.g., content delivery networks (CDNs), cloud serviceplatforms, social media platforms, dark websites) and, in someinstances, flag uses of the unencrypted QC detection data or any othersuitable data that made its way into the external data environment.

In some embodiments, the data monitoring circuitry 220 may be furtherconfigured to generate a QC detection alert control signal in responseto detection of the electronic information related to the encrypted QCdetection data. For example, the data monitoring circuitry 220 may befurther configured to generate a QC detection alert control signal whenthe detected electronic information related to the encrypted QCdetection data comprises decrypted QC detection data that is the same asthe QC detection data. In some embodiments, the QC detection alertcontrol signal may indicate, for example, that the cryptographictechnique used to encrypt the QC detection data has been compromised byquantum computing. In some embodiments, the QC detection alert controlsignal may be configured to instruct, or cause, the cryptographiccircuitry 248 to encrypt or re-encrypt data (e.g., enveloped datastructures stored in one or more internal or third-party data storagedevices) using a PQC cryptographic technique having a cryptostrengththat cannot be compromised by that particular quantum computer. In someembodiments, the QC detection alert control signal may be configured toinstruct, or cause, the UI circuitry 258 to generate QC detection alertGUI data (e.g., an electronic notification, e-mail, pop-up display,audible alarm) and transmit the generated QC detection alert GUI data tothe input-output circuitry 206, and the input-output circuitry 206 maybe configured to receive the QC detection alert GUI data and display thereceived QC detection alert GUI data on one or more display screens.

In some embodiments, wherein the cryptographic circuitry 248 isconfigured to not transmit the encrypted QC detection data, the datamonitoring circuitry 220 may be configured to generate a leakage alertcontrol signal in response to detection of the electronic informationrelated to the encrypted QC detection data. In some embodiments, theleakage alert control signal may indicate, for example, that the QCdetection data was leaked from an internal data environment, when the QCdetection data was leaked from the internal data environment, who leakedthe QC detection data from the internal data environment (e.g., based onthe data lineage of the QC detection data), how the QC detection datawas leaked from the internal data environment, any other suitableinformation, or any combination thereof. In some embodiments, theleakage alert control signal may be configured to instruct, or cause,the communications circuitry 208 to disallow any data to be transmittedout of the internal data environment associated with the leaked QCdetection data. In some embodiments, the leakage alert control signalmay be configured to instruct, or cause, the UI circuitry 258 togenerate leakage alert GUI data (e.g., an electronic notification,e-mail, pop-up display, audible alarm) and transmit the generatedleakage alert GUI data to the input-output circuitry 206, and theinput-output circuitry 206 may be configured to receive the leakagealert GUI data and display the received leakage alert GUI data on one ormore display screens.

In some embodiments, when the detected electronic information related tothe encrypted QC detection data comprises a detected digital signature,the data monitoring circuitry 220 may be further configured to verifythe detected digital signature based on the public cryptographic key. Insome embodiments, the data monitoring circuitry 220 may be furtherconfigured to generate a tampering alert control signal when thedetected electronic information related to the encrypted QC detectiondata further comprises detected payload data that has been digitallysigned based on the detected digital signature, the detected digitalsignature is the same as the QC detection digital signature, and thedetected payload data is different from the QC detection data.

In some embodiments, the tampering alert control signal may indicate,for example, that the QC detection data has been altered but signedusing the same digital signature. For example, the encrypted QCdetection data may comprise QC detection data that has been digitallysigned based on a digital signature (e.g., RSA, such as RSA-PSS; DSA andits elliptic curve variant ECDSA), and the electronic informationrelated to the encrypted QC detection data may comprise payload datathat has been digitally signed based on the digital signature. In someinstances, the payload data may be different from the QC detection data,such as a different fraudulent document digitally signed by the samedigital signature. In some instances, a subset of the payload data maybe the same as a subset of the QC detection data, such as an altereddocument digitally signed by the same digital signature. For example,the QC detection data may comprise a fictitious stock transfer agreementcomprising a first stock transfer attribute indicative of a first amountof transferred shares (e.g., 10 transferred shares), the detectedpayload data may comprise a detected stock transfer agreement comprisinga second stock transfer attribute indicative of a second amount oftransferred shares (e.g., 10,000 transferred shares) different from thefirst amount of transferred shares, and the tampering alert controlsignal may comprise an indication that the fictitious stock transferagreement has been tampered with. In other examples, the detectedpayload data may comprise different buyer or seller information on adigitally signed fictitious electronic mortgage; different ownerinformation on a digitally signed fictitious financial account;different payee or payment amount on a digitally signed fictitiousfinancial transaction (e.g., a fictitious wire transfer, mobile deposit,or electronic check); or any other suitable information.

In some embodiments, the tampering alert control signal may beconfigured to instruct, or cause, the UI circuitry 258 to generatetampering alert GUI data (e.g., an electronic notification, e-mail,pop-up display, audible alarm) and transmit the generated tamperingalert GUI data to the input-output circuitry 206, and the input-outputcircuitry 206 may be configured to receive the tampering alert GUI dataand display the received tampering alert GUI data on one or more displayscreens.

In some embodiments, the data monitoring circuitry 220 includes hardwarecomponents designed or configured to request, receive, process,generate, and transmit data, data structures, control signals, andelectronic information for use in QC detection. In some embodiments, thedata monitoring circuitry 220 may be configured to monitor QC detectiondata, other data, enveloped data structures, any other suitable data orelectronic information, or any combination thereof.

In some embodiments, the data monitoring circuitry 220 may be configuredto monitor a set of data environments for electronic information relatedto the encrypted QC detection data. For example, the data monitoringcircuitry 220 may be configured to monitor a set of internal dataenvironments (e.g., internal information systems, internal datanetworks, internal data storage devices) and, in some instances, flaguses of the QC detection data, the private cryptographic key used toencrypt the QC detection data, or any other suitable data that made itsway into the internal data environment. In another example, the datamonitoring circuitry 220 may be configured to monitor a set of externaldata environments (e.g., content delivery networks (CDNs), cloud serviceplatforms, social media platforms, dark websites) and, in someinstances, flag uses of the unencrypted QC detection data or any othersuitable data that made its way into the external data environment.

In some embodiments, the data monitoring circuitry 220 may be configuredto generate alerts and notifications, such as QC detection alert controlsignals, leakage alert control signals, and tampering alert controlsignals. In some embodiments, the data monitoring circuitry 220 may beconfigured to generate a QC detection alert control signal in responseto detection of the electronic information related to the encrypted QCdetection data. For example, the data monitoring circuitry 220 may beconfigured to generate a QC detection alert control signal when thedetected electronic information related to the encrypted QC detectiondata comprises decrypted QC detection data that is the same as the QCdetection data. In some embodiments, the QC detection alert controlsignal may indicate, for example, that the cryptographic technique usedto encrypt the QC detection data has been compromised by quantumcomputing. In some embodiments, the QC detection alert control signalmay be configured to instruct, or cause, the cryptographic circuitry 248to encrypt or re-encrypt data (e.g., enveloped data structures stored inone or more internal or third-party data storage devices) using a PQCcryptographic technique having a cryptostrength that cannot becompromised by that particular quantum computer. In some embodiments,the QC detection alert control signal may be configured to instruct, orcause, the UI circuitry 258 to generate QC detection alert GUI data(e.g., an electronic notification, e-mail, pop-up display, audiblealarm) and transmit the generated QC detection alert GUI data to theinput-output circuitry 206, and the input-output circuitry 206 may beconfigured to receive the QC detection alert GUI data and display thereceived QC detection alert GUI data on one or more display screens.

In some embodiments, wherein the risk profile generation circuitry 228is configured to not transmit the encrypted QC detection data, the datamonitoring circuitry 220 may be configured to generate a leakage alertcontrol signal in response to detection of the electronic informationrelated to the encrypted QC detection data. In some embodiments, theleakage alert control signal may indicate, for example, that the QCdetection data was leaked from an internal data environment, when the QCdetection data was leaked from the internal data environment, who leakedthe QC detection data from the internal data environment (e.g., based onthe data lineage of the QC detection data), how the QC detection datawas leaked from the internal data environment, any other suitableinformation, or any combination thereof. In some embodiments, theleakage alert control signal may be configured to instruct, or cause,the communications circuitry 208 to disallow any data to be transmittedout of the internal data environment associated with the leaked QCdetection data. In some embodiments, the leakage alert control signalmay be configured to instruct, or cause, the UI circuitry 258 togenerate leakage alert GUI data (e.g., an electronic notification,e-mail, pop-up display, audible alarm) and transmit the generatedleakage alert GUI data to the input-output circuitry 206, and theinput-output circuitry 206 may be configured to receive the leakagealert GUI data and display the received leakage alert GUI data on one ormore display screens.

In some embodiments, when the detected electronic information related tothe encrypted QC detection data comprises a detected digital signature,the data monitoring circuitry 220 may be configured to verify thedetected digital signature based on the public cryptographic key. Insome embodiments, the data monitoring circuitry 220 may be configured togenerate a tampering alert control signal when the detected electronicinformation related to the encrypted QC detection data further comprisesdetected payload data that has been digitally signed based on thedetected digital signature, the detected digital signature is the sameas the QC detection digital signature, and the detected payload data isdifferent from the QC detection data.

In some embodiments, the tampering alert control signal may indicate,for example, that the QC detection data has been altered but signedusing the same digital signature. For example, the encrypted QCdetection data may comprise QC detection data that has been digitallysigned based on a digital signature (e.g., RSA, such as RSA-PSS; DSA andits elliptic curve variant ECDSA), and the electronic informationrelated to the encrypted QC detection data may comprise payload datathat has been digitally signed based on the digital signature. In someinstances, the payload data may be different from the QC detection data,such as a different fraudulent document digitally signed by the samedigital signature. In some instances, a subset of the payload data maybe the same as a subset of the QC detection data, such as an altereddocument digitally signed by the same digital signature. For example,the QC detection data may comprise a fictitious stock transfer agreementcomprising a first stock transfer attribute indicative of a first amountof transferred shares (e.g., 10 transferred shares), the detectedpayload data may comprise a detected stock transfer agreement comprisinga second stock transfer attribute indicative of a second amount oftransferred shares (e.g., 10,000 transferred shares) different from thefirst amount of transferred shares, and the tampering alert controlsignal may comprise an indication that the fictitious stock transferagreement has been tampered with. In other examples, the detectedpayload data may comprise different buyer or seller information on adigitally signed fictitious electronic mortgage; different ownerinformation on a digitally signed fictitious financial account;different payee or payment amount on a digitally signed fictitiousfinancial transaction (e.g., a fictitious wire transfer, mobile deposit,or electronic check); or any other suitable information.

In some embodiments, the tampering alert control signal may beconfigured to instruct, or cause, the UI circuitry 258 to generatetampering alert GUI data (e.g., an electronic notification, e-mail,pop-up display, audible alarm) and transmit the generated tamperingalert GUI data to the input-output circuitry 206, and the input-outputcircuitry 206 may be configured to receive the tampering alert GUI dataand display the received tampering alert GUI data on one or more displayscreens.

In some embodiments, the risk profile generation circuitry 228 includeshardware components designed or configured to request, receive, process,generate, and transmit data, data structures, control signals, andelectronic information for use in QC detection. In some embodiments, therisk profile generation circuitry 228 may be configured to generate apair of asymmetric cryptographic keys comprising a public cryptographickey and a private cryptographic key. In some embodiments, the pair ofasymmetric cryptographic keys may comprise a pair of RSA asymmetriccryptographic keys comprising an RSA public cryptographic key and an RSAprivate cryptographic key. In some embodiments, the pair of asymmetriccryptographic keys may comprise a pair of DH asymmetric cryptographickeys comprising a DH public cryptographic key and a DH privatecryptographic key. In some embodiments, the risk profile generationcircuitry 228 may be configured to generate encrypted QC detection databased on the pair of asymmetric cryptographic keys. In some embodiments,the risk profile generation circuitry 228 may be configured to destroythe private cryptographic key. In other embodiments, the risk profilegeneration circuitry 228 may be configured to destroy both the privatecryptographic key and the public cryptographic key.

In some embodiments, the risk profile generation circuitry 228 may beconfigured to generate the encrypted QC detection data based on adigital signature-based QC detection technique configured to allow fordetection, by the data monitoring circuitry 220, of QC detection data(e.g., a fictitious electronic document) digitally signed using adestroyed RSA private key. In some embodiments, the risk profilegeneration circuitry 228 may be configured to generate the encrypted QCdetection data based on an encryption-based QC detection techniqueconfigured to allow for detection, by the data monitoring circuitry 220,of QC detection data (e.g., disclosed QC detection data that has beentransmitted to a remote device) encrypted using a random AES keyencrypted using a destroyed RSA private key. In some embodiments, therisk profile generation circuitry 228 may be configured to generate theencrypted QC detection data based on a code-sign based QC detectiontechnique configured to allow for detection, by the data monitoringcircuitry 220, of malware code-signed using a destroyed RSA private key.In some embodiments, the risk profile generation circuitry 228 may beconfigured to generate the encrypted QC detection data based on acertificate-based QC detection technique configured to allow fordetection, by the data monitoring circuitry 220, of QC detection data(e.g., a fictitious email certificate or legal sign certificate) signedby an issuer certificate authority using a destroyed RSA private key. Insome embodiments, the risk profile generation circuitry 228 may beconfigured to generate the encrypted QC detection data based on a tamperseal-based QC detection technique configured to allow for detection, bythe data monitoring circuitry 220, of QC detection data (e.g., afraudulent PDF document) with an embedded digital signed object.

The data access monitoring circuitry 222 includes hardware componentsdesigned or configured to request, receive, process, generate, andtransmit data, data structures, control signals, and electronicinformation for use in PQC. In some embodiments, the data accessmonitoring circuitry 222 may be configured to monitor the access ofdata, enveloped data structures, any other suitable data or electronicinformation, or any combination thereof. For example, the data accessmonitoring circuitry 222 may be configured to determine that the datahas been accessed, generate a determination that the data has beenaccessed, and transmit the determination that the data has been accessedto any suitable circuitry, such as the data attribute generationcircuitry 214.

In some embodiments, the data access monitoring circuitry 222 may beconfigured to generate a data access log indicative of a set of dataactivity monitoring information (e.g., database activity monitoringinformation, access credentials, user identification information,machine identification information) associated with electronic access tothe data. For example, the data access monitoring circuitry 222 may beconfigured to generate a data access log comprising a set of timestampsand information indicative of sets of data activity monitoringinformation the data over a period of time (e.g., lifetime of the data;the last three years, or any other suitable period or duration of time),wherein each timestamp in the set of timestamps corresponds to a set ofPQC encryption attributes used to encrypt the data at the timeassociated with the timestamp. In another example, the data accessmonitoring circuitry 222 may be configured to generate the set of dataactivity monitoring information and transmit the set of data activitymonitoring information to the data attribute generation circuitry 214,which may be configured to receive the set of data activity monitoringinformation and generate a data access log based on the set of dataactivity monitoring information.

In some embodiments, the communications circuitry 208 may be configuredto receive the data at a first time, the set of data attributes may be afirst set of data attributes, the data envelope may be a first dataenvelope, the enveloped data structure may be a first enveloped datastructure, and the data access monitoring circuitry 222 may beconfigured to determine that the data has been accessed at a second timelater than the first time. In some embodiments, the data accessmonitoring circuitry 222 may be configured to generate an electronicindication, control signal, metadata, or flag indicating that the datahas been accessed at the second time. In response to the determination(e.g., the electronic indication, control signal, metadata, or flaggenerated by the data access monitoring circuitry 222) that the data hasbeen accessed at the second time, the data attribute generationcircuitry 214 may be configured to generate a second set of dataattributes about the data based on the data and the determination thatthe data has been accessed at the second time, the data envelopegeneration circuitry 216 may be configured to generate a second dataenvelope based on the second set of data attributes, and the datastructure generation circuitry 218 may be configured to generate asecond enveloped data structure based on the second data envelope andthe data. For example, the first set of data attributes may comprise afirst data lineage data attribute indicative of a first data lineage ofthe data, the second set of data attributes may comprise a second datalineage data attribute indicative of a second data lineage of the data,and the first data lineage data attribute may be different from thesecond data lineage data attribute.

The data zone monitoring circuitry 224 includes hardware componentsdesigned or configured to request, receive, process, generate, andtransmit data, data structures, control signals, and electronicinformation for use in PQC. In some embodiments, the data zonemonitoring circuitry 224 may be configured to monitor the data zoneassociated with data, enveloped data structures, any other suitable dataor electronic information, or any combination thereof. For example, thedata zone monitoring circuitry 224 may be configured to determine thatthe data has transitioned from a first data zone to a second data zone,generate a determination that the data has transitioned from the firstdata zone to the second data zone, and transmit the determination thatthe data has transitioned from the first data zone to the second datazone to any suitable circuitry, such as the data attribute generationcircuitry 214.

In some embodiments, the communications circuitry 208 may be configuredto receive the data at a first time, the set of data attributes may be afirst set of data attributes comprising a first data zone data attributeindicative of a first data zone associated with the data, the dataenvelope may be a first data envelope, the enveloped data structure maybe a first enveloped data structure, and the data zone monitoringcircuitry 224 may be configured to determine that the data hastransitioned from the first data zone to a second data zone at a secondtime later than the first time. In some embodiments, the data zonemonitoring circuitry 224 may be configured to generate an electronicindication, control signal, metadata, or flag indicating that the datahas transitioned from the first data zone to the second data zone at thesecond time. In response to the determination (e.g., the electronicindication, control signal, metadata, or flag generated by the data zonemonitoring circuitry 224) that the data has transitioned from the firstdata zone to the second data zone at the second time, the data attributegeneration circuitry 214 may be configured to generate a second set ofdata attributes about the data based on the data and the determinationthat the data has transitioned from the first data zone to the seconddata zone at the second time. The second set of data attributes maycomprise a second data zone data attribute indicative of the second datazone associated with the data, and the second data zone data attributemay be different from the first data zone data attribute. The dataenvelope generation circuitry 216 may be configured to generate a seconddata envelope based on the second set of data attributes. The datastructure generation circuitry 218 may be configured to generate asecond enveloped data structure based on the second data envelope andthe data.

In some embodiments, a first enveloped data structure may comprise dataand a first data envelope comprising a set of data attributes. The dataenvelope generation circuitry 216 may be configured to generate a seconddata envelope comprising the set of data attributes and the risk profiledata structure generated by the risk profile generation circuitry 228.The data structure generation circuitry 218 may be configured togenerate a second enveloped data structure comprising the second dataenvelope and the data.

The policy attribute generation circuitry 226 includes hardwarecomponents designed or configured to request, receive, process,generate, and transmit data, data structures, control signals, andelectronic information for use in PQC. In some embodiments, the policyattribute generation circuitry 226 may be configured to receive,retrieve, or obtain policy information associated with the data. In someembodiments, the policy attribute generation circuitry 226 may beconfigured to retrieve the policy information from a data storagedevice, such as memory 204, one or more of the one or more PQC databases106, the one or more database server devices 114 (including, but notlimited to, one or more data storage devices communicatively coupled,either directly or indirectly, to the one or more database serverdevices 114), the one or more remote server devices 116, the one or moreserver devices 110A-110N, the one or more client devices 112A-112N, anyother suitable device or circuitry, or a combination thereof.

In some embodiments, the policy information may comprise a set oftechnological advancements, such as advancements in materials sciencerelated to quantum computing (e.g., room temperature superconductors),advancements in quantum computing capabilities (e.g., the number ofqubits in a scalable quantum computing architecture, advancementsrelated to Rose's law), any other suitable data, or any combinationthereof. In some embodiments, the policy attribute generation circuitry226 may be configured to decrease the collapse time z described abovewith reference to Table 2 in accordance with the amount and significanceof technological advancements, and thereby decrease the approximate timeto quantum computing threat.

In some embodiments, the policy information may comprise data retentionpolicy information, such as data retention requirements (e.g., alsoreferred to as “security shelf-life”) for various classes of datarecords listed in the FDIC's Records Retention Schedule discussed abovewith reference to Table 1. In some embodiments, the policy informationmay comprise compliance information indicative of a set of compliancerequirements for the data.

In some embodiments, the policy attribute generation circuitry 226 maybe configured to generate a set of policy attributes about the databased on the data and the policy information. In some embodiments, thepolicy attribute generation circuitry 226 may be configured to receive adata envelope comprising a set of data attributes about the data andgenerate the set of policy attributes about the data further based on aset of data attributes about the data. In some embodiments, the policyattribute generation circuitry 226 may be configured to receive,retrieve, or obtain the set of data attributes from another circuitry,such as processing circuitry 202, data attribute generation circuitry214, any other suitable circuitry, or any combination thereof. In someembodiments, the policy attribute generation circuitry 226 may beconfigured to extract, directly or indirectly, the set of policyattributes from an enveloped data structure, such as from a dataenvelope included in the enveloped data structure. In some embodiments,the policy attribute generation circuitry 226 may be configured togenerate the set of policy attributes about the data based on a machinelearning technique, such as a machine learning technique provided orperformed by the machine learning circuitry 254.

In some embodiments, the set of policy attributes may comprise atemporal PQC threat policy attribute indicative of an approximate timeto a quantum computing threat (e.g., collapse time). In someembodiments, the policy attribute generation circuitry 226 may beconfigured to generate the temporal PQC threat policy attribute based ona set of technological advancements included in the policy information.For example, the policy attribute generation circuitry 226 may beconfigured to decrease the collapse time z described above withreference to Table 2 in accordance with the amount and significance ofthe technological advancements. In some embodiments, the policyattribute generation circuitry 226 may be configured to generate thetemporal PQC threat policy attribute based on the receipt of a QCdetection alert control signal, a leakage alert control signal, atampering alert control signal, any other suitable signal or data, orany combination thereof.

In some embodiments, the policy attribute generation circuitry 226 maybe configured to generate the temporal PQC threat policy attribute basedon a quantum computing threat assessment data structure. The quantumcomputing threat assessment data structure may comprise, for example, aquantum computing threat assessment risk level and an electronicrecommendation based on the quantum computing threat assessment risklevel. In some embodiments, the policy attribute generation circuitry226 may be configured to generate the quantum computing threatassessment data structure based on security shelf-life, PQC migrationtime, collapse time, any other suitable parameter, or any combinationthereof. For example, the policy attribute generation circuitry 226 maybe configured to generate a quantum computing threat assessment datastructure in accordance with the quantum computing threat assessmentinequalities shown below in Table 3:

TABLE 3 Example quantum computing threat assessment inequalities thatmay be used by the PQC system described herein to generate quantumcomputing threat assessment risk levels and electronic recommendationsassociated therewith. Quantum Quantum Computing Computing Threat ThreatElectronic Recommendation based on Assessment Assessment QuantumInequality Risk Level Computing Threat Assessment (x + y) < z Risk LevelI: Generate electronic notification indicative Low Risk of quantumcomputing threat assessment risk level I and transmit to client device.(x + y) = z Risk Level II: Generate electronic notification indicativeMedium Risk of quantum computing threat assessment risk level II andtransmit to client device. (x + y) > z Risk Level III: Initiateautomated analysis and processes High Risk to mitigate the quantumcomputing threat because data protected by quantum vulnerable algorithmsat the end of the next y years may be compromised by attacks usingquantum computers in less than x years from that time; generateelectronic notification indicative of quantum computing threatassessment risk level III and transmit to client device. x > z RiskLevel IV: Generate control signal configured to or Immediate instructinformation security system to y > z Remediation perform immediateremediation, such as disconnecting network connections; generateelectronic notification indicative of quantum computing threatassessment risk level IV and transmit to client device.

where x is the security shelf-life (e.g., data retention requirement);where y is the PQC migration time; and where z is the collapse time(e.g., time to quantum computing threat). For example, if the securityshelf-life x is five years and the migration time y is seven years,while the collapse time z is nine years, the policy attribute generationcircuitry 226 may determine that the parameters x, y, and z satisfy thequantum computing threat assessment inequality (x+y) >z and generate aquantum computing threat assessment risk level “Risk Level III: HighRisk” indicating that the cryptographic keys (e.g., secret keys) will becompromised for a duration of three years. The policy attributegeneration circuitry 226 may be further configured to generate anelectronic recommendation based on the quantum computing threatassessment risk level “Risk Level III: High Risk,” wherein theelectronic recommendation comprises an alert, notification, or controlsignal configured to instruct the PQC system to initiate automatedanalysis and planning to mitigate the quantum computing threat now,since data protected by quantum vulnerable tools at the end of the nextseven years may be compromised by quantum attacks in less than fiveyears from that time.

In some embodiments, the set of policy attributes may comprise a valueof the data. In some embodiments, the set of policy attributes maycomprise a longevity of the data. For example, the policy attributegeneration circuitry 226 may be configured to generate the longevity ofthe data based on data retention policy information included in thepolicy information. In some embodiments, the set of policy attributesmay comprise a cryptostrength of the data. In some embodiments, the setof policy attributes may comprise a set of vulnerability scan results.For example, the policy attribute generation circuitry 226 may receivethe set of vulnerability scan results from the vulnerability scancircuitry 230.

The risk profile generation circuitry 228 includes hardware componentsdesigned or configured to request, receive, process, generate, andtransmit data, data structures, control signals, and electronicinformation for use in PQC. In some embodiments, the risk profilegeneration circuitry 228 may be configured to generate a risk profiledata structure indicative of a vulnerability of the data in a PQC dataenvironment. In some embodiments, the risk profile generation circuitry228 may be configured to generate the risk profile data structure basedon the set of policy attributes. In some embodiments, the risk profiledata structure may comprise a plurality of risk profile data elementsindicative of a vulnerability of the data in a PQC data environment. Insome embodiments, the risk profile data structure may comprise avulnerability score data structure (e.g., a vulnerability score datastructure received from the vulnerability score generation circuitry232), a vulnerability score explanation data structure (e.g., avulnerability score explanation data structure received from thevulnerability score generation circuitry 232), a compliance score datastructure (e.g., a compliance score data structure received from thecompliance score generation circuitry 234), a compliance scoreexplanation data structure (e.g., a compliance score explanation datastructure received from the compliance score generation circuitry 234),any other suitable data, or any combination thereof.

In some embodiments, the risk profile generation circuitry 228 may beconfigured to generate QC detection data. In some embodiments, the QCdetection data may comprise fictitious data, a fictitious code-signingcertificate, any other suitable data, or any combination thereof. Insome embodiments, the risk profile generation circuitry 228 may beconfigured to generate the QC detection data based on a machine learningtechnique, such as a machine learning technique provided or performed bythe machine learning circuitry 254. In some embodiments, the riskprofile generation circuitry 228 may be configured to update the threatin response to receipt of a quantum computing detection alert controlsignal (e.g., indicating that: a quantum computer has compromisedRSA-512; a quantum computer has compromised RSA-1024; a quantum computerhas compromised RSA-2048), a leakage alert control signal, a tamperingalert control signal, any other suitable signal or data, or anycombination thereof.

The vulnerability scan circuitry 230 includes hardware componentsdesigned or configured to request, receive, process, generate, andtransmit data, data structures, control signals, and electronicinformation for use in PQC. In some embodiments, the vulnerability scancircuitry 230 may comprise, or be communicatively coupled to, one ormore hardware scanners (e.g., scanner appliances), software scanners(e.g., virtual scanners), cloud-based scanners (e.g., cloud agents,Internet scanners, cloud connectors), passive scanners, out-of-bandsensors, container sensors, APIs, any other suitable components, or anycombinations thereof.

In some embodiments, the vulnerability scan circuitry 230 may beconfigured to provide vulnerability identification, vulnerabilityassessment, vulnerability management, application scanning, any othersuitable functionality, and any combination thereof. In someembodiments, the vulnerability scan circuitry 230 may be configured tolocate, identify, assess, prioritize, and mitigate vulnerabilities.These vulnerabilities include, but are not limited to, SQL injection,cross-site scripting (XSS), cross-site request forgery (CSRF), anduniform resource locator (URL) redirection.

In some embodiments, the vulnerability scan circuitry 230 may beconfigured to perform a vulnerability scan of the data; and generate aset of vulnerability scan results, wherein the set of policy attributescomprises the set of vulnerability scan results. For example, thevulnerability scan circuitry 230 may be configured to perform avulnerability scan of the data and generate the set of vulnerabilityscan results based on the performance of the vulnerability scan. In someembodiments, the vulnerability scan circuitry 230 may be configured to:transmit, to a third-party circuitry or service provider, a request toperform a vulnerability scan of the data; receive a set of vulnerabilityscan results from the third-party circuitry or service provider; andgenerate the set of vulnerability scan results based on the set ofvulnerability scan results.

The vulnerability score generation circuitry 232 includes hardwarecomponents designed or configured to request, receive, process,generate, and transmit data, data structures, control signals, andelectronic information for use in PQC. In some embodiments, thevulnerability score generation circuitry 232 may be configured togenerate a vulnerability score data structure based on the set of policyattributes, wherein the risk profile data structure comprises thevulnerability score data structure.

In some embodiments, the vulnerability score data structure may comprisea vulnerability score value indicative of a percentage of vulnerabilityof the data in the PQC data environment. In some embodiments, thevulnerability score generation circuitry 232 may be configured togenerate a normalized vulnerability score value based on a normalizationof the vulnerability score value to a common scale (e.g., 0.0 to 1.0;0.00 to 100.00; 0.0% to 100.0%).

In some embodiments, the vulnerability score data structure may comprisea vulnerability score range comprising a minimum vulnerability scorevalue, a maximum vulnerability score value, a median vulnerability scorevalue, a mean vulnerability score value, a first quartile vulnerabilityscore value, a third quartile vulnerability score value, aninterquartile vulnerability score range between the first quartilevulnerability score value and the third quartile vulnerability scorevalue, any other suitable value, metric, or range, or any combinationthereof. In some embodiments, the vulnerability score generationcircuitry 232 may be configured to generate a normalized vulnerabilityscore range based on a normalization of the vulnerability score range toa common scale.

In some embodiments, the vulnerability score generation circuitry 232may be configured to generate a vulnerability score explanation datastructure indicative of an explanation of the vulnerability score datastructure, wherein the risk profile data structure comprises thevulnerability score explanation data structure. In some embodiments, thevulnerability score explanation data structure may be a localinterpretable model-agnostic explanations (LIME) data structureindicative of one or more identified vulnerabilities, where thosevulnerabilities were located (e.g., at the time of identification), howand why those vulnerabilities were identified, how and why thosevulnerabilities were assessed, how and why those vulnerabilities whereprioritized, and how and why those vulnerabilities were mitigated.

The compliance score generation circuitry 234 includes hardwarecomponents designed or configured to request, receive, process,generate, and transmit data, data structures, control signals, andelectronic information for use in PQC. In some embodiments, thecompliance score generation circuitry 234 may be configured to generatea compliance score data structure. For example, the compliance scoregeneration circuitry 234 may be configured to receive (e.g., from policyattribute generation circuitry 226 or any other suitable device orcircuitry) policy information comprising compliance informationindicative of a set of compliance requirements for the data. Thecompliance score generation circuitry 234 may be configured to generatea compliance score explanation data structure based on the vulnerabilityscore data structure and the compliance information, wherein the riskprofile data structure comprises the compliance score data structure.

In some embodiments, the compliance score data structure comprises acompliance score value indicative of a percentage of compliance of thedata to the set of compliance requirements. In some embodiments, thecompliance score generation circuitry 234 may be configured to generatea normalized compliance score value based on a normalization of thecompliance score value to a common scale (e.g., 0.0 to 1.0; 0.00 to100.00; 0.0% to 100.0%). In some embodiments, the normalized compliancescore value may be different from the normalized vulnerability scorevalue.

In some embodiments, the compliance score data structure may comprise acompliance score range comprising a minimum compliance score value, amaximum compliance score value, a median compliance score value, a meancompliance score value, a first quartile compliance score value, a thirdquartile compliance score value, an interquartile compliance score rangebetween the first quartile compliance score value and the third quartilecompliance score value, any other suitable value, metric, or range, orany combination thereof. In some embodiments, the compliance scoregeneration circuitry 234 may be configured to generate a normalizedcompliance score range based on a normalization of the compliance scorerange to a common scale. In some embodiments, the normalized compliancescore range may be different from the normalized vulnerability scorerange.

In some embodiments, the compliance score generation circuitry 234 maybe configured to generate a compliance score explanation data structureindicative of an explanation of the compliance score data structure,wherein the risk profile data structure comprises the compliance scoreexplanation data structure. In some embodiments, the compliance scoreexplanation data structure may be a LIME data structure indicative ofone or more identified compliance attributes, where those complianceattributes were located (e.g., at the time of identification), how andwhy those compliance attributes were identified, how and why thosecompliance attributes were assessed, how and why those complianceattributes where prioritized, and how and why those complianceattributes were mitigated.

The cryptographic performance circuitry 236 includes hardware componentsdesigned or configured to request, receive, process, generate, andtransmit data, data structures, control signals, and electronicinformation for use in PQC. In some embodiments, the cryptographicperformance circuitry 236 may be configured to retrieve cryptographicperformance information associated with a set of non-PQC cryptographictechniques, a set of PQC cryptographic techniques, or both. In thisregard, the cryptographic performance circuitry 236 may include, forexample, non-PQC cryptographic performance circuitry 238 and PQCcryptographic performance circuitry 240.

The non-PQC cryptographic performance circuitry 238 includes hardwarecomponents designed or configured to request, receive, process,generate, and transmit data, data structures, control signals, andelectronic information for use in PQC. In some embodiments, the non-PQCcryptographic performance circuitry 238 may be configured to generateand retrieve non-PQC cryptographic performance information associatedwith a set of non-PQC cryptographic techniques. In some embodiments, thenon-PQC cryptographic performance circuitry 238 may be configured toretrieve the non-PQC cryptographic performance information from one ormore of the one or more PQC server devices 104, the one or more PQCdatabases 106, any other suitable device, or any combination thereof. Insome embodiments, the non-PQC cryptographic performance circuitry 238may be configured to generate the non-PQC cryptographic performanceinformation based on a machine learning technique, such as a machinelearning technique provided or performed by the machine learningcircuitry 254.

In some embodiments, the non-PQC cryptographic performance informationmay comprise a set of non-PQC cryptographic performance attributes foreach non-PQC cryptographic technique (e.g., each variant of each non-PQCcryptographic algorithm) in the set of non-PQC cryptographic techniques.In some embodiments, each non-PQC cryptographic technique in the set ofnon-PQC cryptographic techniques may be a variant of a non-PQCcryptographic algorithm. In some embodiments, the set of non-PQCcryptographic performance attributes may comprise key space, key length,and runtime resource requirements (e.g., memory, time) for varied datablock sizes (e.g., 100 kilobytes, 10 megabytes, 1 gigabyte). In someembodiments, the set of non-PQC cryptographic performance attributes maycomprise key sizes (e.g., public, private, or both), time taken, keygeneration, encryption, decryption, signature generation, signatureverification, length, ciphertext, signature, cost, computationalefficiency, memory requirements, how configurable the non-PQCcryptographic technique is, whether the parameters of the non-PQCcryptographic technique are tunable, how the non-PQC cryptographictechnique fits in with standard protocols, whether the non-PQCcryptographic technique resistant to misuse, and then the simplicity ofmanaging the non-PQC cryptographic technique.

In some embodiments, the set of non-PQC cryptographic performanceattributes may comprise a CPU utilization for each non-PQC cryptographictechnique in the set of non-PQC cryptographic techniques. In someembodiments, the set of non-PQC cryptographic performance attributes maycomprise a memory utilization for each non-PQC cryptographic techniquein the set of non-PQC cryptographic techniques. In some embodiments, theset of non-PQC cryptographic performance attributes may comprise anencryption time (e.g., a determined processing time needed to encrypt aunit of data, such as seconds per megabyte of data) for each non-PQCcryptographic technique in the set of non-PQC cryptographic techniques.In some embodiments, the set of non-PQC cryptographic performanceattributes may comprise a decryption time (e.g., a determined processingtime needed to decrypt a unit of encrypted data, such as seconds permegabyte of data) for each non-PQC cryptographic technique in the set ofnon-PQC cryptographic techniques. In some embodiments, the set ofnon-PQC cryptographic performance attributes may comprise a verificationtime (e.g., a determined processing time needed to verify a unit ofencrypted data, such as seconds per megabyte of data) for each non-PQCcryptographic technique in the set of non-PQC cryptographic techniques.In some embodiments, the set of non-PQC cryptographic performanceattributes may comprise a key length (e.g., key size) for each non-PQCcryptographic technique in the set of non-PQC cryptographic techniques.In some embodiments, the set of non-PQC cryptographic performanceattributes may comprise a payload size for each non-PQC cryptographictechnique in the set of non-PQC cryptographic techniques. In someembodiments, the set of non-PQC cryptographic performance attributes maycomprise a payload longevity for each non-PQC cryptographic technique inthe set of non-PQC cryptographic techniques. In some embodiments, theset of non-PQC cryptographic performance attributes may comprise a setof policy attributes for each non-PQC cryptographic technique in the setof non-PQC cryptographic techniques. In some embodiments, the set ofnon-PQC cryptographic performance attributes may comprise an informationclassification for each non-PQC cryptographic technique in the set ofnon-PQC cryptographic techniques. In some embodiments, the set ofnon-PQC cryptographic performance attributes may comprise a mode ofoperation for each non-PQC cryptographic technique in the set of non-PQCcryptographic techniques.

The PQC cryptographic performance circuitry 240 includes hardwarecomponents designed or configured to request, receive, process,generate, and transmit data, data structures, control signals, andelectronic information for use in PQC. In some embodiments, the PQCcryptographic performance circuitry 240 may be configured to generateand retrieve PQC cryptographic performance information associated with aset of PQC cryptographic techniques. In some embodiments, the PQCcryptographic performance circuitry 240 may be configured to retrievethe PQC cryptographic performance information from one or more of theone or more PQC server devices 104, the one or more PQC databases 106,any other suitable device, or any combination thereof.

In some embodiments, the PQC cryptographic performance circuitry 240 maybe configured to generate the PQC cryptographic performance information.For example, the PQC cryptographic performance circuitry 240 may beconfigured to generate information indicative of the algorithm andimplementation scale for each PQC cryptographic technique in the set ofPQC cryptographic techniques. In another example, the PQC cryptographicperformance circuitry 240 may be configured to generate electronicinformation indicative of the efficiency, performance, and deterministicoperation of each PQC cryptographic technique in the set of PQCcryptographic techniques. In another example, the PQC cryptographicperformance circuitry 240 may be configured to perform a cryptanalysisfor each PQC cryptographic technique in the set of PQC cryptographictechniques and generate, based on the cryptanalysis, a confidence datastructure comprising a confidence score for each PQC cryptographictechnique in the set of PQC cryptographic techniques. In yet anotherexample, the PQC cryptographic performance circuitry 240 may beconfigured to generate electronic information indicative of theusability and interoperability of each PQC cryptographic technique inthe set of PQC cryptographic techniques. In some embodiments, the PQCcryptographic performance circuitry 240 may be configured to generatethe PQC cryptographic performance information by capturing performancemetrics reflecting the performance of the various PQC cryptographictechnique implementations. In some embodiments, the PQC cryptographicperformance circuitry 240 may be configured to generate the PQCcryptographic performance information based on a machine learningtechnique, such as a machine learning technique provided or performed bythe machine learning circuitry 254. The PQC cryptographic performancecircuitry 240 may use the PQC cryptographic performance information andthe various data components thereof to improve machine understanding ofhow these PQC cryptographic techniques may can be used the PQC system102. In some instances, the PQC cryptographic performance circuitry 240may use the captured performance metrics to evaluate otherimplementations of these or other PQC cryptographic techniques.

In some embodiments, the PQC cryptographic performance information maycomprise a set of PQC cryptographic performance attributes for each PQCcryptographic technique (e.g., each variant of each PQC cryptographicalgorithm) in the set of PQC cryptographic techniques. In someembodiments, each PQC cryptographic technique in the set of PQCcryptographic techniques may be a variant of a PQC cryptographicalgorithm. In some embodiments, the set of PQC cryptographic performanceattributes may comprise key space, key length, and runtime resourcerequirements (e.g., memory, time) for varied data block sizes (e.g., 100kilobytes, 10 megabytes, 1 gigabyte). In some embodiments, the set ofPQC cryptographic performance attributes may comprise key sizes (e.g.,public, private, or both), time taken, key generation, encryption,decryption, signature generation, signature verification, length,ciphertext, signature, cost, computational efficiency, memoryrequirements, how configurable the PQC cryptographic technique is,whether the parameters of the PQC cryptographic technique are tunable,how the PQC cryptographic technique fits in with standard protocols,whether the PQC cryptographic technique resistant to misuse, and thenthe simplicity of managing the PQC cryptographic technique.

In some embodiments, the set of PQC cryptographic performance attributesmay comprise a CPU utilization for each PQC cryptographic technique inthe set of PQC cryptographic techniques. In some embodiments, the set ofPQC cryptographic performance attributes may comprise a memoryutilization for each PQC cryptographic technique in the set of PQCcryptographic techniques. In some embodiments, the set of PQCcryptographic performance attributes may comprise an encryption time(e.g., a determined processing time needed to encrypt a unit of data,such as seconds per megabyte of data) for each PQC cryptographictechnique in the set of PQC cryptographic techniques. In someembodiments, the set of PQC cryptographic performance attributes maycomprise a decryption time (e.g., a determined processing time needed todecrypt a unit of encrypted data, such as seconds per megabyte of data)for each PQC cryptographic technique in the set of PQC cryptographictechniques. In some embodiments, the set of PQC cryptographicperformance attributes may comprise a verification time (e.g., adetermined processing time needed to verify a unit of encrypted data,such as seconds per megabyte of data) for each PQC cryptographictechnique in the set of PQC cryptographic techniques. In someembodiments, the set of PQC cryptographic performance attributes maycomprise a key length (e.g., key size) for each PQC cryptographictechnique in the set of PQC cryptographic techniques. In someembodiments, the set of PQC cryptographic performance attributes maycomprise a payload size for each PQC cryptographic technique in the setof PQC cryptographic techniques. In some embodiments, the set of PQCcryptographic performance attributes may comprise a payload longevityfor each PQC cryptographic technique in the set of PQC cryptographictechniques. In some embodiments, the set of PQC cryptographicperformance attributes may comprise a set of policy attributes for eachPQC cryptographic technique in the set of PQC cryptographic techniques.In some embodiments, the set of PQC cryptographic performance attributesmay comprise an information classification for each PQC cryptographictechnique in the set of PQC cryptographic techniques. In someembodiments, the set of PQC cryptographic performance attributes maycomprise a mode of operation for each PQC cryptographic technique in theset of PQC cryptographic techniques.

The cryptographic attribute generation circuitry 242 includes hardwarecomponents designed or configured to request, receive, process,generate, and transmit data, data structures, control signals, andelectronic information for use in PQC. In some embodiments, thecryptographic attribute generation circuitry 242 may be configured togenerate a set of non-PQC encryption attributes for encrypting the data,a set of PQC encryption attributes for encrypting the data, or both. Inthis regard, the cryptographic attribute generation circuitry 242 mayinclude, for example, non-PQC cryptographic attribute generationcircuitry 244 and PQC cryptographic attribute generation circuitry 246.

The non-PQC cryptographic attribute generation circuitry 244 includeshardware components designed or configured to request, receive, process,generate, and transmit data, data structures, control signals, andelectronic information for use in PQC. In some embodiments, the non-PQCcryptographic attribute generation circuitry 244 may be configured togenerate a set of non-PQC encryption attributes for encrypting the data.In some embodiments, the non-PQC cryptographic attribute generationcircuitry 244 may be configured to generate the set of non-PQCencryption attributes based on the set of data attributes, the riskprofile data structure, and the non-PQC cryptographic performanceinformation. In some embodiments, the non-PQC cryptographic attributegeneration circuitry 244 may be configured to receive, retrieve, orobtain the set of data attributes from another circuitry, such asprocessing circuitry 202, data attribute generation circuitry 214, anyother suitable circuitry, or any combination thereof. In someembodiments, the non-PQC cryptographic attribute generation circuitry244 may be configured to extract, directly or indirectly, the set ofpolicy attributes from an enveloped data structure, such as from a dataenvelope included in the enveloped data structure. In some embodiments,the non-PQC cryptographic attribute generation circuitry 244 may beconfigured to receive, retrieve, or obtain the risk profile datastructure from another circuitry, such as processing circuitry 202, riskprofile generation circuitry 228, any other suitable circuitry, or anycombination thereof. In some embodiments, the non-PQC cryptographicattribute generation circuitry 244 may be configured to extract,directly or indirectly, the risk profile data structure from anenveloped data structure, such as from a data envelope included in theenveloped data structure. In some embodiments, the non-PQC cryptographicattribute generation circuitry 244 may be configured to generate the setof non-PQC encryption attributes based on based on a machine learningtechnique, such as a machine learning technique provided or performed bythe machine learning circuitry 254.

The PQC cryptographic attribute generation circuitry 246 includeshardware components designed or configured to request, receive, process,generate, and transmit data, data structures, control signals, andelectronic information for use in PQC. In some embodiments, the PQCcryptographic attribute generation circuitry 246 may be configured togenerate a set of PQC encryption attributes for encrypting the data. Insome embodiments, the PQC cryptographic attribute generation circuitry246 may be configured to generate the set of PQC encryption attributesbased on the set of data attributes, the risk profile data structure,and the PQC cryptographic performance information. In some embodiments,the PQC cryptographic attribute generation circuitry 246 may beconfigured to receive, retrieve, or obtain the set of data attributesfrom another circuitry, such as processing circuitry 202, data attributegeneration circuitry 214, any other suitable circuitry, or anycombination thereof. In some embodiments, the PQC cryptographicattribute generation circuitry 246 may be configured to extract,directly or indirectly, the set of policy attributes from an envelopeddata structure, such as from a data envelope included in the envelopeddata structure. In some embodiments, the PQC cryptographic attributegeneration circuitry 246 may be configured to receive, retrieve, orobtain the risk profile data structure from another circuitry, such asprocessing circuitry 202, risk profile generation circuitry 228, anyother suitable circuitry, or any combination thereof. In someembodiments, the PQC cryptographic attribute generation circuitry 246may be configured to extract, directly or indirectly, the risk profiledata structure from an enveloped data structure, such as from a dataenvelope included in the enveloped data structure. In some embodiments,the PQC cryptographic attribute generation circuitry 246 may beconfigured to generate the set of PQC encryption attributes based onbased on a machine learning technique, such as a machine learningtechnique provided or performed by the machine learning circuitry 254.

In some embodiments, the PQC cryptographic attribute generationcircuitry 246 may be configured to generate an allowable transactiontime for encryption of the data. In some embodiments, the PQCcryptographic attribute generation circuitry 246 may be configured togenerate the set of PQC encryption attributes further based on theallowable transaction time.

In some embodiments, the PQC cryptographic attribute generationcircuitry 246 may be configured to generate the PQC cryptographicperformance information. In some embodiments, the PQC cryptographicperformance information may comprise a set of PQC cryptographicperformance attributes for each PQC cryptographic technique in the setof PQC cryptographic techniques. In some instances, a PQC cryptographictechnique in the set of PQC cryptographic techniques may be a variant ofa PQC cryptographic algorithm. In some instances, a PQC cryptographictechnique in the set of PQC cryptographic techniques may be a variant ofa PQC communications channel cryptographic technique. In some instances,a PQC cryptographic technique in the set of PQC cryptographic techniquesmay be a combination of a first variant of a PQC cryptographic algorithmand a second variant of a PQC communications channel cryptographictechnique.

In some embodiments, the PQC cryptographic attribute generationcircuitry 246 may be configured to generate a set of PQC cryptographicperformance attribute weightage values based on the set of dataattributes, the risk profile data structure, and the PQC cryptographicperformance information. The set of PQC cryptographic performanceattribute weightage values may comprise a PQC cryptographic performanceattribute weightage value w_(i) for each cryptographic performanceattribute in the set of PQC cryptographic performance attributes for aparticular PQC cryptographic technique, where i is an integer rangingfrom 1 to N, and where N is an integer that is greater than or equalto 1. In some embodiments, each PQC cryptographic performance attributeweightage value w_(i) in the set of PQC cryptographic performanceattribute weightage values may correspond to a respective PQCcryptographic performance attribute in the set of PQC cryptographicperformance attributes. For example, the set of PQC cryptographicperformance attributes may comprise NPQC cryptographic performanceattributes, and the set of PQC cryptographic performance attributeweightage values may comprise N PQC cryptographic performance attributeweightage values, where each PQC cryptographic performance attributeweightage value w_(i) in the set of N PQC cryptographic performanceattributes corresponds to a respective cryptographic performanceattribute in the set of NPQC cryptographic performance attributes forthe particular PQC cryptographic technique.

In some embodiments, the PQC cryptographic attribute generationcircuitry 246 may be configured to generate a set of PQC cryptographicperformance attribute scores for each PQC cryptographic performanceattribute in the set of PQC cryptographic performance attributes andeach PQC cryptographic technique in the set of PQC cryptographictechniques based on the set of data attributes, the risk profile datastructure, and the PQC cryptographic performance information. The set ofPQC cryptographic performance attribute scores may comprise a PQCcryptographic performance attribute score s_(i,j,k) for eachcryptographic performance attribute in the set of PQC cryptographicperformance attributes for a particular PQC cryptographic technique,where i refers to the i-th PQC cryptographic performance attribute inthe set of PQC cryptographic performance attributes, where i is aninteger ranging from 1 to N, and where Nis an integer that is greaterthan or equal to 1; where j refers to the j-th variant of a PQCcryptographic algorithm in the set of PQC cryptographic techniques,where j is an integer ranging from 1 to M, and where M is an integerthat is greater than or equal to 1; and where k refers to the k-th PQCcryptographic algorithm in the set of PQC cryptographic techniques,where k is an integer ranging from 1 to P, and where P is an integerthat is greater than or equal to 1.

In some embodiments, the PQC cryptographic attribute generationcircuitry 246 may be configured to generate a set of weighted PQCcryptographic performance attribute scores based on the set of PQCcryptographic performance attribute scores and the set of PQCcryptographic performance attribute weightage values. In someembodiments, the PQC cryptographic attribute generation circuitry 246may be configured to generate the set of weighted PQC cryptographicperformance attribute scores according to equation 1 below:S _(i,j,k) =w _(i) ×s _(i,j,k)  (1)

where w_(i) is the PQC cryptographic performance attribute weightagevalue for each cryptographic performance attribute in the set of PQCcryptographic performance attributes; s_(i,j,k) is the PQC cryptographicperformance attribute score for each cryptographic performanceattribute; and S_(i,j,k) is the weighted PQC cryptographic performanceattribute score, where i refers to the i-th PQC cryptographicperformance attribute in the set of PQC cryptographic performanceattributes, where i is an integer ranging from 1 to N, and where Nis aninteger that is greater than or equal to 1; where j refers to the j-thvariant of a PQC cryptographic algorithm in the set of PQC cryptographictechniques, where j is an integer ranging from 1 to M, and where M is aninteger that is greater than or equal to 1; and where k refers to thek-th PQC cryptographic algorithm in the set of PQC cryptographictechniques, where k is an integer ranging from 1 to P, and where P is aninteger that is greater than or equal to 1.

In some embodiments, the PQC cryptographic attribute generationcircuitry 246 may be configured to generate a set of PQC cryptographictechnique scores based on the set of weighted PQC cryptographicperformance attribute scores. In some embodiments, each PQCcryptographic technique score in the set of PQC cryptographic techniquescores may correspond to a respective PQC cryptographic technique in theset of PQC cryptographic techniques. In some embodiments, the PQCcryptographic attribute generation circuitry 246 may be configured togenerate set of PQC cryptographic technique scores according to equation2 below:

$\begin{matrix}{{T_{j,k} = {\sum\limits_{i = 1}^{N}S_{i,j,k}}}\;} & (2)\end{matrix}$

where T_(j,k) is the PQC cryptographic technique score for each PQCcryptographic technique (e.g., each variant of each PQC cryptographicalgorithm); and S_(i,j,k) is the weighted PQC cryptographic performanceattribute score, where i refers to the i-th PQC cryptographicperformance attribute in the set of PQC cryptographic performanceattributes, where i is an integer ranging from 1 to N, and where Nis aninteger that is greater than or equal to 1; where j refers to the j-thvariant of a PQC cryptographic algorithm in the set of PQC cryptographictechniques, where j is an integer ranging from 1 to M, and where M is aninteger that is greater than or equal to 1; and where k refers to thek-th PQC cryptographic algorithm in the set of PQC cryptographictechniques, where k is an integer ranging from 1 to P, and where P is aninteger that is greater than or equal to 1.

In some embodiments, the set of PQC cryptographic technique scores maycomprise a PQC cryptographic technique score range comprising a minimumPQC cryptographic technique score, a maximum PQC cryptographic techniquescore, a median PQC cryptographic technique score, a mean PQCcryptographic technique score, a first quartile PQC cryptographictechnique score, a third quartile PQC cryptographic technique score, aninterquartile PQC cryptographic technique score range between the firstquartile PQC cryptographic technique score and the third quartile PQCcryptographic technique score, any other suitable value, metric, orrange, or any combination thereof.

In some embodiments, the PQC cryptographic attribute generationcircuitry 246 may be configured to generate the set of PQC encryptionattributes for encrypting the data based on the set of PQC cryptographictechnique scores. For example, the set of PQC cryptographic techniquescores may comprise a maximum PQC cryptographic technique score, and thePQC cryptographic attribute generation circuitry 246 may be configuredto generate the set of PQC encryption attributes for encrypting the databased on an optimal PQC cryptographic technique that corresponds to themaximum PQC cryptographic technique score. In another example, the setof PQC cryptographic technique scores may comprise subset of high PQCcryptographic technique scores (e.g., the top three PQC cryptographictechnique scores), and the PQC cryptographic attribute generationcircuitry 246 may be configured to generate the set of PQC encryptionattributes for encrypting the data based on an optimal PQC cryptographictechnique that corresponds to a PQC cryptographic technique score in thesubset of high PQC cryptographic technique scores having the highestcryptostrength. In another example, the set of PQC cryptographictechnique scores may comprise a median PQC cryptographic techniquescore, the set of PQC cryptographic technique scores may comprise asubset of PQC cryptographic technique scores above the median PQCcryptographic technique score, and the PQC cryptographic attributegeneration circuitry 246 may be configured to generate the set of PQCencryption attributes for encrypting the data based on an optima; PQCcryptographic technique that corresponds to a PQC cryptographictechnique score in the subset of PQC cryptographic technique scoresabove the median PQC cryptographic technique score having the lowesttransaction time. In yet another example, the set of PQC cryptographictechnique scores may comprise a third quartile subset of PQCcryptographic technique scores, and the PQC cryptographic attributegeneration circuitry 246 may be configured to generate the set of PQCencryption attributes for encrypting the data based on an optimal PQCcryptographic technique that corresponds to a PQC cryptographictechnique score in the third quartile subset of PQC cryptographictechnique scores above the median PQC cryptographic technique scorehaving the lowest CPU utilization, the lowest memory utilization, thelowest latency, the lowest time for operation, or a combination thereof.

The cryptographic circuitry 248 includes hardware components designed orconfigured to request, receive, process, generate, and transmit data,data structures, control signals, and electronic information for use inPQC. In some embodiments, the cryptographic circuitry 248 may beconfigured to encrypt data based on a set of PQC encryption attributes,a set of PQC encryption attributes, or both. In this regard, thecryptographic circuitry 248 may include, for example, non-PQCcryptographic circuitry 250 and PQC cryptographic circuitry 252. In someembodiments, where the first portion of the electronic communicationcomprises a cryptographic data attribute indicative of a symmetriccryptographic technique and the second portion of the electroniccommunication comprises a symmetric cryptographic key, such as an AESsymmetric cryptographic key, the cryptographic circuitry 248 may beconfigured to authenticate a session (e.g., perform a cryptographichandshake) with the client device over the non-PQC communicationschannel based on the symmetric cryptographic key that was transmitted tothe client device over the PQC communications channel.

In some embodiments, the cryptographic circuitry 248 may be configuredto authenticate a session (e.g., perform a cryptographic handshake) withthe client device over the non-PQC communications channel based on thequantum cryptographic key that was transmitted to the client device overthe quantum communications channel. In some embodiments, thecryptographic circuitry 248 may be configured to encrypt the secondportion of the electronic communication based on the quantumcryptographic key before transmission to the client device over the PQCcommunications channel.

The non-PQC cryptographic circuitry 250 includes hardware componentsdesigned or configured to request, receive, process, generate, andtransmit data, data structures, control signals, and electronicinformation for use in PQC. In some embodiments, the non-PQCcryptographic circuitry 250 may be configured to encrypt the data basedon the set of non-PQC encryption attributes.

The PQC cryptographic circuitry 252 includes hardware componentsdesigned or configured to request, receive, process, generate, andtransmit data, data structures, control signals, and electronicinformation for use in PQC. In some embodiments, the PQC cryptographiccircuitry 252 may be configured to encrypt the data based on the set ofPQC encryption attributes.

In some embodiments, the data may have been encrypted using a non-PQCcryptographic technique, and the PQC cryptographic attribute generationcircuitry 246 may be configured to determine a PQC cryptographictechnique based on a set of data attributes, a risk profile datastructure, PQC cryptographic performance information associated with aset of PQC cryptographic techniques, or a combination thereof. The PQCcryptographic circuitry 252 may be configured to encrypt the data usingthe PQC cryptographic technique.

In some embodiments, the data may have been encrypted using a first PQCcryptographic technique, and the PQC cryptographic attribute generationcircuitry 246 may be configured to determine a PQC cryptographictechnique based on a set of data attributes, a risk profile datastructure, PQC cryptographic performance information associated with aset of PQC cryptographic techniques, or a combination thereof. The PQCcryptographic circuitry 252 may be configured to encrypt the data usingthe second PQC cryptographic technique.

In some embodiments, the communications circuitry 208 may be configuredto receive the data at a first time, the set of data attributes may be afirst set of data attributes comprising a first cryptographic dataattribute indicative of a first cryptographic technique used to encryptthe data, the data envelope may be a first data envelope, the envelopeddata structure may be a first enveloped data structure, and the PQCcryptographic circuitry 252 may be configured to encrypt the data usinga second cryptographic technique at a second time later than the firsttime. In response to an encryption of the data using the secondcryptographic technique at the second time, the data attributegeneration circuitry 214 may be configured to generate a second set ofdata attributes about the data based on the data and the encryption ofthe data using the second cryptographic technique at the second time.The second set of data attributes may comprise a second cryptographicdata attribute indicative of the second cryptographic technique used toencrypt the data at the second time, and the second cryptographic dataattribute may be different from the first cryptographic data attribute.The data envelope generation circuitry 216 may be configured to generatea second data envelope based on the second set of data attributes. Thedata structure generation circuitry may be configured to generate asecond enveloped data structure based on the second data envelope andthe data. In one example, the first cryptographic technique may be anon-PQC cryptographic technique, and the second cryptographic techniquemay be a PQC cryptographic technique. In another example, the firstcryptographic technique may be a first PQC cryptographic technique, andthe second cryptographic technique may be a second PQC cryptographictechnique different from the first PQC cryptographic technique(including, but not limited to, a different variant of the same PQCcryptographic algorithm).

In some embodiments, the cryptographic circuitry 248 may be configuredto encrypt data using various recommended cryptographic techniques, suchas non-PQC cryptographic techniques, PQC cryptographic techniques, andhybrid PQC cryptographic techniques (e.g., hybrid PQC cryptographictechnique={PQC cryptographic technique, Non-PQC cryptographictechnique}). For example, the recommended cryptographic technique maycomprise a hybrid PQC cryptographic mode, such as a signature-basedhybrid PQC cryptographic mode consisting of a non-PQC cryptographicsignature and a PQC cryptographic signature, where the hybrid PQCcryptographic mode is valid only if both the non-PQC cryptographicsignature and the PQC cryptographic signature are valid (e.g., the PQCsystem may perform validation of the non-PQC cryptographic signatureaccording to FIPS 140-3; the PQC system may perform validation of thePQC cryptographic signature using multiple public-key algorithms forX.509 certificates, such as quantum-resistant X.509 Multiple Public KeyAlgorithm Certificates).

In some embodiments, the cryptographic circuitry 248 may recommenddifferent cryptographic techniques for encrypting data used by differentlines of business (LOBs) or entities. For example, the cryptographiccircuitry 248 may recommend a first PQC cryptographic technique forencrypting data used by a first LOB; a second PQC cryptographictechnique for encrypting data used by a second LOB; a non-PQCcryptographic technique for encrypting data used by a third LOB; and ahybrid PQC cryptographic technique for encrypting data used by a fourthLOB.

The machine learning circuitry 254 includes hardware components designedor configured to request, receive, process, generate, and transmit data,data structures, control signals, and electronic information for use inPQC. In some embodiments, the machine learning circuitry 254 may beconfigured to provide machine learning techniques, any other suitablefunctionality, or any combination thereof. For example, the machinelearning circuitry 254 may be configured to provide a machine learningtechnique, machine learning functionality, or both to the data attributegeneration circuitry 214, data envelope generation circuitry 216, datastructure generation circuitry 218, data monitoring circuitry 220,policy attribute generation circuitry 226, risk profile generationcircuitry 228, cryptographic performance circuitry 236, cryptographicattribute generation circuitry 242, any other circuitry, or anycombination thereof. In some embodiments, the machine learning circuitry254 may be configured to determine the machine learning technique fromamong a set of machine learning techniques. In some embodiments, themachine learning circuitry 230 may be configured to determine (e.g.,predict) which cryptographic technique (e.g., non-PQC cryptographictechnique, PQC cryptographic technique, or hybrid PQC cryptographictechnique) to use for data encryption based on test data, productiondata, and any of the parameters described herein.

In some embodiments, the machine learning circuitry 254 may beconfigured to provide a machine learning technique, machine learningfunctionality, or both to the data attribute generation circuitry 214for use in generation of the set of data attributes about the data. Insome embodiments, the machine learning circuitry 254 may be configuredto provide a machine learning technique, machine learning functionality,or both to the policy attribute generation circuitry 226 for use ingeneration of the set of policy attributes about the data. In someembodiments, the machine learning circuitry 254 may be configured toprovide a machine learning technique, machine learning functionality, orboth to the PQC cryptographic performance circuitry 240 for use ingeneration of the PQC cryptographic performance information. In someembodiments, the machine learning circuitry 254 may be configured toprovide a machine learning technique, machine learning functionality, orboth to the PQC cryptographic attribute generation circuitry 246 for usein generation of the set of PQC encryption attributes. In someembodiments, the machine learning circuitry 254 may be configured toprovide a machine learning technique, machine learning functionality, orboth to risk profile generation circuitry 228 for use in generation ofthe QC detection data.

The data storage circuitry 256 includes hardware components designed orconfigured to request, receive, process, generate, store, and transmitdata, data structures, control signals, and electronic information foruse in PQC. In some embodiments, the data storage circuitry 256 may beconfigured to store data (e.g., unencrypted data, encrypted data,decrypted data, re-encrypted data, double encrypted data, data accesscontrol information, bitstreams of data, links or pointers thereto),data attributes, data envelopes, enveloped data structures, policyinformation, policy attributes, risk profile data structures, non-PQCcryptographic techniques, non-PQC cryptographic performance information,non-PQC encryption attributes, PQC cryptographic performanceinformation, PQC cryptographic techniques, PQC encryption attributes,symmetric cryptographic keys, asymmetric cryptographic keys, any othersuitable data or electronic information, or combinations thereof in adata storage device, a database management system, any other suitablestorage device or system, or any combination thereof.

For example, the data storage circuitry 256 may be configured to storean enveloped data structure in a data storage device, a databasemanagement system, or a combination thereof. In some embodiments, thedata storage circuitry 256 may be configured to store the data, datastructures, control signals, and electronic information in the datastorage device, the database management system, or both in real-time andwithout user interactivity.

In some embodiments, the data storage device may comprise, or beimplemented as, memory 204, one or more of the one or more PQC databases106, the one or more database server devices 114 (including, but notlimited to, one or more data storage devices communicatively coupled,either directly or indirectly, to the one or more database serverdevices 114), the one or more remote server devices 116, the one or moreserver devices 110A-110N, the one or more client devices 112A-112N, anyother suitable device or circuitry, or a combination thereof. In someembodiments, the database management system may comprise, or beimplemented as, a database management system (DBMS), such as arelational DMBS (RDBMS) data warehouse, a first non-relational DBMS(e.g., Hadoop distributed file system (HDFS), Hbase), a secondnon-relational DBMS (e.g., content management systems), a datavisualization device, a data mart (e.g., online analytical processing(OLAP) cube), a real-time analytical RDBMS, any other suitable device orcircuitry, or a combination thereof. In some embodiments, the datastorage device, the database management system, or both may comprise, orbe implemented as, one or more decentralized storage devices, such as acloud storage device or system.

The UI circuitry 258 includes hardware components designed or configuredto generate graphical user interface (GUI) data configured to bedisplayed by a display device. For instance, the UI circuitry 258 mayinclude hardware components designed or configured to generate GUI databased on any embodiment or combination of embodiments described withreference to FIGS. 1-8. In some embodiments, the UI circuitry 258 may beconfigured to generate GUI data and transmit the generated GUI data tothe input-output circuitry 206, and the input-output circuitry 206 maybe configured to receive the GUI data and display the received GUI dataon one or more display screens. In some embodiments, the UI circuitry258 may include hardware components designed or configured to generatethe GUI data based on one or more portions of the data; data attributes;data envelopes; enveloped data structures; policy information; policyattributes; risk profile data structures; non-PQC cryptographictechniques; non-PQC cryptographic performance information; non-PQCencryption attributes; PQC cryptographic performance information; PQCcryptographic techniques; PQC encryption attributes; symmetriccryptographic keys; asymmetric cryptographic keys; quantum particles;quantum cryptographic keys; quantum one-time pads; any other suitabledata, data structures, electronic information, or quantum information;any links or pointers thereto; and any combinations thereof. The GUIdata may comprise, for example, data attribute GUI data generated basedon the set of data attributes; risk profile GUI data generated based onthe risk profile data structure; PQC optimization GUI data generatedbased on the PQC cryptographic performance information (including, butnot limited to, the set of PQC cryptographic performance attributes),the set of PQC encryption attributes, or both; and data monitoring GUIdata generated based on the monitoring of enveloped data structures,electronic indications of changes in the monitored enveloped datastructures, any other suitable data, or any combination thereof.

In some embodiments, the UI circuitry 258 may be configured to generatea data attribute GUI based on the set of data attributes. In someembodiments, the UI circuitry 258 may be configured to generate a riskprofile GUI data based on the risk profile data structure. In someembodiments, the UI circuitry 258 may be configured to generate a PQCoptimization GUI based on the PQC cryptographic performance information(including, but not limited to, the set of PQC cryptographic performanceattributes), the set of PQC encryption attributes, or both. In someembodiments, the UI circuitry 258 may be configured to generate a datamonitoring GUI based on the monitoring of enveloped data structures,electronic indications of changes in the monitored enveloped datastructures, any other suitable data, or any combination thereof. In someembodiments, the communications circuitry 208 may be configured totransmit the data attribute GUI, risk profile GUI, PQC optimization GUI,data monitoring GUI, or a combination thereof to a client device fordisplay by the client device.

It should also be appreciated that, in some embodiments, each of thedata attribute generation circuitry 214, data envelope generationcircuitry 216, data structure generation circuitry 218, data monitoringcircuitry 220, data access monitoring circuitry 222, data zonemonitoring circuitry 224, policy attribute generation circuitry 226,risk profile generation circuitry 228, vulnerability scan circuitry 230,vulnerability score generation circuitry 232, compliance scoregeneration circuitry 234, cryptographic performance circuitry 236,non-PQC cryptographic performance circuitry 238, PQC cryptographicperformance circuitry 240, cryptographic attribute generation circuitry242, non-PQC cryptographic attribute generation circuitry 244, PQCcryptographic attribute generation circuitry 246, cryptographiccircuitry 248, non-PQC cryptographic circuitry 250, PQC cryptographiccircuitry 252, machine learning circuitry 254, data storage circuitry256, and UI circuitry 258 may include a separate processor, speciallyconfigured field programmable gate array (FPGA), ASIC, or cloud utilityto perform the above functions.

In some embodiments, the hardware components described above withreference to data attribute generation circuitry 214, data envelopegeneration circuitry 216, data structure generation circuitry 218, datamonitoring circuitry 220, data access monitoring circuitry 222, datazone monitoring circuitry 224, policy attribute generation circuitry226, risk profile generation circuitry 228, vulnerability scan circuitry230, vulnerability score generation circuitry 232, compliance scoregeneration circuitry 234, cryptographic performance circuitry 236,non-PQC cryptographic performance circuitry 238, PQC cryptographicperformance circuitry 240, cryptographic attribute generation circuitry242, non-PQC cryptographic attribute generation circuitry 244, PQCcryptographic attribute generation circuitry 246, cryptographiccircuitry 248, non-PQC cryptographic circuitry 250, PQC cryptographiccircuitry 252, machine learning circuitry 254, data storage circuitry256, and UI circuitry 258, may, for instance, utilize PQC callbackcircuitry 207, communications circuitry 208, or any suitable wired orwireless communications path to communicate with a node device, a serverdevice (e.g., one or more of server devices 110A-110N), a client device(e.g., one or more of client devices 112A-112N), a database serverdevice (e.g., one or more of database server devices 114), a remoteserver device (e.g., one or more of remote server devices 116),processing circuitry 202, memory 204, input-output circuitry 206, thePQC callback circuitry of another apparatus (e.g., the PQC callbackcircuitry 207 of a separate apparatus implementing one or more portionsof apparatus 200 shown in FIG. 2A), the PQC shim circuitry of anotherapparatus (e.g., the PQC shim circuitry 260 of a separate apparatusimplementing one or more portions of apparatus 280 shown in FIG. 2B),the communications circuitry of another apparatus (e.g., thecommunications circuitry 208 of a separate apparatus implementing one ormore portions of apparatus 200, 280, or 290), each other, or any othersuitable circuitry or device.

In some embodiments, one or more of the data attribute generationcircuitry 214, data envelope generation circuitry 216, data structuregeneration circuitry 218, data monitoring circuitry 220, data accessmonitoring circuitry 222, data zone monitoring circuitry 224, policyattribute generation circuitry 226, risk profile generation circuitry228, vulnerability scan circuitry 230, vulnerability score generationcircuitry 232, compliance score generation circuitry 234, cryptographicperformance circuitry 236, non-PQC cryptographic performance circuitry238, PQC cryptographic performance circuitry 240, cryptographicattribute generation circuitry 242, non-PQC cryptographic attributegeneration circuitry 244, PQC cryptographic attribute generationcircuitry 246, cryptographic circuitry 248, non-PQC cryptographiccircuitry 250, PQC cryptographic circuitry 252, machine learningcircuitry 254, data storage circuitry 256, and UI circuitry 258 may behosted locally by the apparatus 200.

In some embodiments, one or more of the data attribute generationcircuitry 214, data envelope generation circuitry 216, data structuregeneration circuitry 218, data monitoring circuitry 220, data accessmonitoring circuitry 222, data zone monitoring circuitry 224, policyattribute generation circuitry 226, risk profile generation circuitry228, vulnerability scan circuitry 230, vulnerability score generationcircuitry 232, compliance score generation circuitry 234, cryptographicperformance circuitry 236, non-PQC cryptographic performance circuitry238, PQC cryptographic performance circuitry 240, cryptographicattribute generation circuitry 242, non-PQC cryptographic attributegeneration circuitry 244, PQC cryptographic attribute generationcircuitry 246, cryptographic circuitry 248, non-PQC cryptographiccircuitry 250, PQC cryptographic circuitry 252, machine learningcircuitry 254, data storage circuitry 256, and UI circuitry 258 may behosted remotely (e.g., by one or more cloud servers) and thus need notphysically reside on the apparatus 200. Thus, some or all of thefunctionality described herein may be provided by a third-partycircuitry. For example, the apparatus 200 may access one or morethird-party circuitries via a networked connection configured totransmit and receive data and electronic information between theapparatus 200 and the third-party circuitries. In turn, the apparatus200 may be in remote communication with one or more of the dataattribute generation circuitry 214, data envelope generation circuitry216, data structure generation circuitry 218, data monitoring circuitry220, data access monitoring circuitry 222, data zone monitoringcircuitry 224, policy attribute generation circuitry 226, risk profilegeneration circuitry 228, vulnerability scan circuitry 230,vulnerability score generation circuitry 232, compliance scoregeneration circuitry 234, cryptographic performance circuitry 236,non-PQC cryptographic performance circuitry 238, PQC cryptographicperformance circuitry 240, cryptographic attribute generation circuitry242, non-PQC cryptographic attribute generation circuitry 244, PQCcryptographic attribute generation circuitry 246, cryptographiccircuitry 248, non-PQC cryptographic circuitry 250, PQC cryptographiccircuitry 252, machine learning circuitry 254, data storage circuitry256, and UI circuitry 258.

As illustrated in FIG. 2B, an apparatus 280 is shown that represents anexample server device 110, client device 112, database server device114, remote server device 116, any other suitable device, or acombination thereof. The apparatus 280 may include one or more ofprocessing circuitry 202, memory 204, input-output circuitry 206,communications circuitry 208 (including, but not limited to, classicalcommunications circuitry 210 and quantum communications circuitry 212),cryptographic circuitry 248 (including, but not limited to, non-PQCcryptographic circuitry 250, PQC cryptographic circuitry 252, and, insome instances, PQC shim circuitry 260, wherein PQC shim circuitry 260comprises PQC cryptographic circuitry 252), gateway circuitry 264,concentrator circuitry 266, store controller circuitry 268, terminalmanager circuitry 270, PoS software upgrade circuitry 272, hardwaresecurity module (HSM) circuitry 274, any other suitable circuitry, orany combination thereof. It will be understood, however, that additionalcomponents providing additional functionality may be included in theapparatus 280 without departing from the scope of the presentdisclosure. The apparatus 280 may be involved in execution of variousoperations described above with respect to FIGS. 1 and 2A and below withrespect to FIGS. 3-8.

In some embodiments, such as in embodiments where the apparatus 280 is aclassical, non-PQC device that does not include PQC cryptographiccircuitry, the apparatus 280 may be modified to include PQC shimcircuitry 260. The PQC shim circuitry 260 may include hardwarecomponents designed or configured to allow communication with a PQCcallback (e.g., PQC callback circuitry 207 shown in FIG. 2A). The PQCshim circuitry 260 includes hardware components designed or configuredto request, receive, process, generate, and transmit data, datastructures, control signals, and electronic information for use in PQC.For example, PQC shim circuitry 260 may be configured to provide PQCcommunications channel-based cryptographic techniques, such as thetransmission and receipt of sensitive portions (e.g., payloads) ofelectronic communications to a PQC callback over one or more PQCcommunications channels. In some embodiments, the PQC shim circuitry 260may be installed in a network layer of the apparatus 280. In someembodiments, the PQC shim circuitry 260 may comprise the PQCcryptographic circuitry 252.

In some embodiments, the first portion of the electronic communicationmay comprise a PQC request data structure indicative of a request for anacknowledgment or confirmation that the client device (e.g., theapparatus 280) is configured to communicate over a PQC communicationschannel. The client device may be configured to communicate over a PQCcommunications channel if the client device, or a PQC add-on device(e.g., apparatus 290 shown in FIG. 2C) coupled to the client device,comprises the PQC cryptographic circuitry 252, either without the PQCshim circuitry 260 or as a part of the PQC shim circuitry 260. Forexample, the classical communications circuitry 210 may be configured toreceive the first portion of the electronic communication comprising thePQC request data structure from the server device (e.g., the apparatus200 shown in FIG. 2A) over the non-PQC communications channel.

In some embodiments, if the client device is configured to communicateover a PQC communications channel, the classical communicationscircuitry 210 may be configured to transmit, to the server device, a PQCacknowledgement data structure indicating that it is configured tocommunicate over a PQC communications channel. In response to receipt ofthe PQC acknowledgement data structure by the server device, the PQCcallback circuitry 207 of the server device may be configured totransmit the second portion of the electronic communication to theclient device over the PQC communications channel. Subsequently, the PQCcryptographic circuitry 252, either without the PQC shim circuitry 260or as a part of the PQC shim circuitry 260, may be configured to receivethe second portion of the electronic communication from the serverdevice over the PQC communications channel.

In some embodiments, if the client device is not configured tocommunicate over a PQC communications channel, the classicalcommunications circuitry 210 may be configured to transmit, to theserver device, a PQC negative-acknowledgement data structure indicatingthat it is not configured to communicate over a PQC communicationschannel. Alternatively, if the client device is not configured tocommunicate over a PQC communications channel, the classicalcommunications circuitry 210 may be configured to not transmit anyresponse to the server device.

In some embodiments, in response to receipt of the PQCnegative-acknowledgement data structure by the server device, or thelack of receipt of a response by the server device after a predeterminedtime period (e.g., a predetermined period of inactivity or predeterminedelapsed time, such as a timeout), the PQC callback circuitry 207 of theserver device may be configured to transmit a PQC indicator datastructure to the client device over the PQC communications channel. ThePQC indicator data structure may comprise a link to a PQC shimconfigured to allow communication with the PQC callback circuitry 207over the PQC communications channel. Subsequently, the classicalcommunications circuitry 210 may be configured to transmit, to theserver device, a PQC acknowledgement data structure indicating that itis configured to communicate over a PQC communications channel.

In some embodiments, the PQC indicator data structure may furtheridentify the quantum communications channel and indicate that a quantumcryptographic key is to be transmitted over the quantum communicationschannel. The PQC indicator data structure may comprise a link or pointerto the quantum communications channel, a header that identifies thequantum communications channel and comprises other identification androuting information. In some embodiments, the PQC indicator datastructure may comprise a link to the quantum cryptographic key. In someembodiments, the first portion of the electronic communication maycomprise a TLS extension comprising the PQC indicator data structure. Inanother example, the first portion of the electronic communication maycomprise an ISO 8583 extension comprising the PQC indicator datastructure. In another example, the PQC indicator data structure may be,or comprise, or be indicated by, a quantum flag value. In anotherexample, the PQC indicator data structure may comprise a link to aquantum electronic agreement (e.g., a bilateral agreement between thePQC system and the client device to exchange quantum information overthe quantum communications channel) comprising the PQC indicator datastructure.

In some embodiments, the first portion of the electronic communicationmay comprise a quantum request data structure indicative of a requestfor an acknowledgment or confirmation that the client device (e.g., theapparatus 280) is configured to communicate over a quantumcommunications channel. The client device may be configured tocommunicate over a quantum communications channel if the client device,or a PQC add-on device (e.g., apparatus 290 shown in FIG. 2C) coupled tothe client device, comprises the quantum communications circuitry 212.For example, the classical communications circuitry 210 may beconfigured to receive the first portion of the electronic communicationcomprising the quantum request data structure from the server device(e.g., the apparatus 200 shown in FIG. 2A) over the non-PQCcommunications channel.

In some embodiments, if the client device is configured to communicateover a quantum communications channel, the classical communicationscircuitry 210 may be configured to transmit, to the server device, aquantum acknowledgement data structure indicating that it is configuredto communicate over a quantum communications channel. In response toreceipt of the quantum acknowledgement data structure by the serverdevice, the quantum communications circuitry 212 of the server devicemay be configured to transmit the quantum cryptographic key to theclient device over the quantum communications channel. The quantumcommunications circuitry 212 may be configured to receive the quantumcryptographic key from the server device over the quantum communicationschannel. Subsequently, the cryptographic circuitry 248 may be configuredto authenticate a session (e.g., perform a cryptographic handshake) withthe client device over the non-PQC communications channel based on thequantum cryptographic key that was transmitted to the client device overthe quantum communications channel.

In some embodiments, if the client device is not configured tocommunicate over a quantum communications channel, the classicalcommunications circuitry 210 may be configured to transmit, to theserver device, a quantum negative-acknowledgement data structureindicating that the client device is not configured to communicate overa quantum communications channel. Alternatively, if the client device isnot configured to communicate over a quantum communications channel, theclassical communications circuitry 210 may be configured to not transmitany response to the server device. In some embodiments, in response toreceipt of the quantum negative-acknowledgement data structure by theserver device, or the lack of receipt of a response by the server deviceafter a predetermined time period (e.g., a predetermined period ofinactivity or predetermined elapsed time, such as a timeout), thequantum communications circuitry 212 of the server device may beconfigured to not transmit the quantum cryptographic key or the secondportion of the electronic communication to the client device.

The gateway circuitry 264 includes hardware components designed orconfigured to request, receive, process, generate, and transmit data,data structures, control signals, and electronic information for use inPQC. In some embodiments, the gateway circuitry 264 may be configured toprovide transactions management, payment processing, any other suitablefunctionality, and any combination thereof for one or more PoS devicesor other devices communicatively coupled to the apparatus 280.

The concentrator circuitry 266 includes hardware components designed orconfigured to request, receive, process, generate, and transmit data,data structures, control signals, and electronic information for use inPQC. In some embodiments, the concentrator circuitry 266 may beconfigured to connect multiple PoS devices or other devices to theapparatus 280. For example, the concentrator circuitry 266 may beconfigured to provide communications management, connectivity, any othersuitable functionality, and any combination thereof for one or more PoSdevices or other devices communicatively coupled to the apparatus 280.

The store controller circuitry 268 includes hardware components designedor configured to request, receive, process, generate, and transmit data,data structures, control signals, and electronic information for use inPQC. In some embodiments, the store controller circuitry 268 may beconfigured to provide applications, services, any other suitablefunctionality, and any combination thereof for one or more PoS devicesor other devices communicatively coupled to the apparatus 280.

The terminal manager circuitry 270 includes hardware components designedor configured to request, receive, process, generate, and transmit data,data structures, control signals, and electronic information for use inPQC. In some embodiments, the terminal manager circuitry 270 may beconfigured to provide terminal management, terminal monitoring, terminalcontrol, terminal updating, any other suitable functionality, and anycombination thereof for one or more PoS devices or other devicescommunicatively coupled to the apparatus 280.

The PoS software upgrade circuitry 272 includes hardware componentsdesigned or configured to request, receive, process, generate, andtransmit data, data structures, control signals, and electronicinformation for use in PQC. In some embodiments, the PoS softwareupgrade circuitry 272 may be configured to provide software upgradingfunctionality, proxy upgrade functionality (e.g., upgrade to a PQC orPQC-related proxy), any other suitable functionality, and anycombination thereof for one or more PoS devices or other devicescommunicatively coupled to the apparatus 280. In some embodiments, thePoS software upgrade circuitry 272 may be configured to upgrade the PoSproxy of connected PoS devices.

The HSM circuitry 274 includes hardened, tamper-resistant hardwarecomponents designed or configured to request, receive, process,generate, and transmit data, data structures, control signals, andelectronic information for use in PQC. In some embodiments, the HSMcircuitry 274 may be configured to provide: protection for cryptographickeys, customer personal identification numbers (PINs), magnetic stripedata, EMV (originally Europay, Mastercard, and Visa) chip data, andmobile application counterparts thereof (e.g., virtual debit cards andcredit cards stored in a user's mobile wallet); native cryptographicsupport for card scheme payment applications; any other suitablefunctionality; and any combination thereof for one or more PoS devicesor other devices communicatively coupled to the apparatus 280. In someembodiments, the HSM circuitry 274 may be configured to provide:personal identification number (PIN) generation, management andvalidation; PIN block translation during the network switching of ATMand PoS transactions; card, user, and cryptogram validation duringpayment transaction processing; payment credential issuing for paymentcards and mobile applications; point-to-point encryption (P2PE) keymanagement and secure data decryption; secure key sharing with thirdparties to facilitate secure communications; any other suitablefunctionality; and any combination thereof.

It should also be appreciated that, in some embodiments, each of thecryptographic circuitry 248, non-PQC cryptographic circuitry 250, PQCcryptographic circuitry 252, PQC shim circuitry 260, gateway circuitry264, concentrator circuitry 266, store controller circuitry 268,terminal manager circuitry 270, PoS software upgrade circuitry 272, andHSM circuitry 274 may include a separate processor, specially configuredFPGA, ASIC, or cloud utility to perform the above functions.

In some embodiments, the hardware components described above withreference to cryptographic circuitry 248, non-PQC cryptographiccircuitry 250, PQC cryptographic circuitry 252, PQC shim circuitry 260,gateway circuitry 264, concentrator circuitry 266, store controllercircuitry 268, terminal manager circuitry 270, PoS software upgradecircuitry 272, and HSM circuitry 274, may, for instance, utilizecommunications circuitry 208 or any suitable wired or wirelesscommunications path to communicate with a node device, a server device(e.g., one or more of server devices 110A-110N), a client device (e.g.,one or more of client devices 112A-112N), a database server device(e.g., one or more of database server devices 114), a remote serverdevice (e.g., one or more of remote server devices 116), processingcircuitry 202, memory 204, input-output circuitry 206, the PQC callbackcircuitry of another apparatus (e.g., the PQC callback circuitry 207 ofa separate apparatus implementing one or more portions of apparatus 200shown in FIG. 2A), the PQC shim circuitry of another apparatus (e.g.,the PQC shim circuitry 260 of a separate apparatus implementing one ormore portions of apparatus 280), the communications circuitry of anotherapparatus (e.g., the communications circuitry 208 of a separateapparatus implementing one or more portions of apparatus 200, 280, or290), each other, or any other suitable circuitry or device.

In some embodiments, one or more of the cryptographic circuitry 248,non-PQC cryptographic circuitry 250, PQC cryptographic circuitry 252,PQC shim circuitry 260, gateway circuitry 264, concentrator circuitry266, store controller circuitry 268, terminal manager circuitry 270, PoSsoftware upgrade circuitry 272, and HSM circuitry 274 may be hostedlocally by the apparatus 280.

In some embodiments, one or more of the cryptographic circuitry 248,non-PQC cryptographic circuitry 250, PQC cryptographic circuitry 252,PQC shim circuitry 260, gateway circuitry 264, concentrator circuitry266, store controller circuitry 268, terminal manager circuitry 270, PoSsoftware upgrade circuitry 272, and HSM circuitry 274 may be hostedremotely (e.g., by one or more cloud servers) and thus need notphysically reside on the apparatus 280. Thus, some or all of thefunctionality described herein may be provided by a third-partycircuitry. For example, the apparatus 280 may access one or morethird-party circuitries via a networked connection configured totransmit and receive data and electronic information between theapparatus 280 and the third-party circuitries. In turn, the apparatus280 may be in remote communication with one or more of the cryptographiccircuitry 248, non-PQC cryptographic circuitry 250, PQC cryptographiccircuitry 252, PQC shim circuitry 260, gateway circuitry 264,concentrator circuitry 266, store controller circuitry 268, terminalmanager circuitry 270, PoS software upgrade circuitry 272, and HSMcircuitry 274.

As illustrated in FIG. 2C, an apparatus 290 is shown that represents anexample PQC add-on device configured to be communicatively coupled(e.g., wirelessly connected, electrically connected) to a client device,such as a server device 110, client device 112, database server device114, remote server device 116, any other suitable device, or acombination thereof. In some embodiments, the apparatus 290 may be a PQCperipheral device communicatively coupled to the client device. In someembodiments, the apparatus 290 may be, or comprise, a PQC ASIC installedwithin a housing of the client device.

In some embodiments, the apparatus 290 may include one or more ofprocessing circuitry 202, memory 204, input-output circuitry 206,communications circuitry 208 (including, but not limited to, classicalcommunications circuitry 210 and quantum communications circuitry 212),cryptographic circuitry 248 (including, but not limited to, non-PQCcryptographic circuitry 250 and PQC cryptographic circuitry 252), anyother suitable circuitry, or any combination thereof. It will beunderstood, however, that additional components providing additionalfunctionality may be included in the apparatus 290 without departingfrom the scope of the present disclosure. The apparatus 290 may beinvolved in execution of various operations described above with respectto FIGS. 1 and 2A and below with respect to FIGS. 3-8.

In some embodiments, the apparatus 290 may hardware components designedor configured to allow communication with a PQC callback (e.g., PQCcallback circuitry 207 shown in FIG. 2A). The apparatus 290 includeshardware components designed or configured to request, receive, process,generate, and transmit data, data structures, control signals, andelectronic information for use in PQC. For example, the apparatus 290may be configured to provide PQC communications channel-basedcryptographic techniques, such as the transmission and receipt ofsensitive portions (e.g., payloads) of electronic communications to aPQC callback over one or more PQC communications channels.

It should also be appreciated that, in some embodiments, each of thecryptographic circuitry 248, non-PQC cryptographic circuitry 250, PQCcryptographic circuitry 252 may include a separate processor, speciallyconfigured FPGA, ASIC, or cloud utility to perform the above functions.

In some embodiments, the hardware components described above withreference to cryptographic circuitry 248, non-PQC cryptographiccircuitry 250, and PQC cryptographic circuitry 252, may, for instance,utilize communications circuitry 208 or any suitable wired or wirelesscommunications path to communicate with a node device, a server device(e.g., one or more of server devices 110A-110N), a client device (e.g.,one or more of client devices 112A-112N), a database server device(e.g., one or more of database server devices 114), a remote serverdevice (e.g., one or more of remote server devices 116), processingcircuitry 202, memory 204, input-output circuitry 206, the PQC callbackcircuitry of another apparatus (e.g., the PQC callback circuitry 207 ofa separate apparatus implementing one or more portions of apparatus 200shown in FIG. 2A), the PQC shim circuitry of another apparatus (e.g.,the PQC shim circuitry 260 of a separate apparatus implementing one ormore portions of apparatus 280 shown in FIG. 2B), the communicationscircuitry of another apparatus (e.g., the communications circuitry 208of a separate apparatus implementing one or more portions of apparatus200, 280, or 290), each other, or any other suitable circuitry ordevice.

In some embodiments, one or more of the cryptographic circuitry 248,non-PQC cryptographic circuitry 250, PQC cryptographic circuitry 252 maybe hosted locally by the apparatus 290.

In some embodiments, one or more of the cryptographic circuitry 248,non-PQC cryptographic circuitry 250, PQC cryptographic circuitry 252 maybe hosted remotely (e.g., by one or more cloud servers) and thus neednot physically reside on the apparatus 290. Thus, some or all of thefunctionality described herein may be provided by a third-partycircuitry. For example, the apparatus 290 may access one or morethird-party circuitries via a networked connection configured totransmit and receive data and electronic information between theapparatus 290 and the third-party circuitries. In turn, the apparatus290 may be in remote communication with one or more of the cryptographiccircuitry 248, non-PQC cryptographic circuitry 250, PQC cryptographiccircuitry 252.

Although some of these components of apparatuses 200, 280, and 290 aredescribed with respect to their functional capabilities, it should beunderstood that the particular implementations necessarily include theuse of particular hardware to implement such functional capabilities. Itshould also be understood that certain of these components may includesimilar or common hardware. For example, two sets of circuitries mayboth leverage use of the same processor, network interface, quantumcommunications interface, optoelectronic components, storage medium,machine learning circuitry, or the like to perform their associatedfunctions, such that duplicate hardware is not required for each set ofcircuitries. It should also be appreciated that, in some embodiments,one or more of these components may include a separate processor,specially configured FPGA, ASIC, or cloud utility to perform itscorresponding functions as described herein.

The use of the term “circuitry” as used herein with respect tocomponents of apparatuses 200, 280, and 290 includes particular hardwareconfigured to perform the functions associated with respective circuitrydescribed herein. While the term “circuitry” should be understoodbroadly to include hardware, in some embodiments, circuitry may alsoinclude software for configuring the hardware. For example, in someembodiments, “circuitry” may include processing circuitry, storagemedia, network interfaces, quantum interfaces, input-output devices,optoelectronic components, and other components. In some embodiments,other elements of apparatuses 200, 280, and 290 may provide orsupplement the functionality of particular circuitry. For example, theprocessing circuitry 202 may provide processing functionality, memory204 may provide storage functionality, classical communicationscircuitry 210 may provide network interface functionality, and quantumcommunications circuitry 212 may provide quantum interface functionalityamong other features.

In some embodiments, various components of one or more of theapparatuses 200, 280, or 290 may be hosted remotely (e.g., by one ormore cloud servers) and thus need not physically reside on thecorresponding apparatus 200, 280, or 290. Thus, some or all of thefunctionality described herein may be provided by third-party circuitry.For example, a given apparatus 200, 280, or 290 may access one or morethird-party circuitries via any sort of networked connection thatfacilitates transmission of data and electronic information between theapparatus 200, 280, or 290 and the third-party circuitries. In turn,that apparatus 200, 280, or 290 may be in remote communication with oneor more of the other components described above as being comprised bythe apparatus 200, 280, or 290.

As will be appreciated, computer program instructions and/or other typeof code may be loaded onto a computer, processor or other programmableapparatus's circuitry to produce a machine, such that the computer,processor, or other programmable circuitry that executes the code on themachine creates the means for implementing various functions describedherein.

As described above and as will be appreciated based on this disclosure,embodiments of the present disclosure may be configured as systems,apparatuses, methods, optoelectronic devices, mobile devices, backendnetwork devices, computer program products, other suitable devices, andcombinations thereof. Accordingly, embodiments may comprise variousmeans including entirely of hardware or any combination of software withhardware. Furthermore, embodiments may take the form of a computerprogram product on at least one non-transitory computer-readable storagemedium having computer-readable program instructions (e.g., computersoftware) embodied in the storage medium. Any suitable computer-readablestorage medium may be utilized including non-transitory hard disks,CD-ROMs, flash memory, optical storage devices, or magnetic storagedevices. As will be appreciated, any computer-executable program codeinstructions, any other type of code described herein, and anycombination thereof may be loaded onto a computer, processor or otherprogrammable apparatus's circuitry to produce a machine, such that thecomputer, processor, or other programmable circuitry that executes thecode on the machine creates the means for implementing variousfunctions, including the functions described herein.

The one or more server devices 110A-110N, one or more client devices112A-112N, one or more database server devices 114, and one or moreremote server devices 116 described with reference to FIG. 1 may beembodied by one or more computing devices, servers, data storagedevices, or systems that also may include processing circuitry, memory,input-output circuitry, and communications circuitry. For example, aserver device 110 may be a database server on which computer code (e.g.,C, C++, C#, java, a structured query language (SQL), a data querylanguage (DQL), a data definition language (DDL), a data controllanguage (DCL), a data manipulation language (DML)) is running orotherwise being executed by processing circuitry. In another example, aclient device 112 may be a smartphone on which an app (e.g., a mobiledatabase app) is running or otherwise being executed by processingcircuitry. As it relates to operations described in the presentdisclosure, the functioning of these devices may utilize componentssimilar to the similarly named components described above with referenceto FIG. 2. Additional description of the mechanics of these componentsis omitted for the sake of brevity. These device elements, operatingtogether, provide the respective computing systems with thefunctionality necessary to facilitate the communication of data with thePQC system described herein.

FIGS. 3-5 illustrate example PQC system architectures configured toperform various operations in accordance with some example embodimentsdescribed herein.

FIG. 3A illustrates an example PQC system architecture 300 configured toperform various operations in accordance with some example embodimentsdescribed herein. The example PQC system architecture 300 may comprise,for example, PQC system 302 and client device 320.

In some embodiments, the PQC system 302 may comprise, for example, oneor more data storage devices 306 comprising search and other functions,one or more PQC server devices 304, one or more non-PQC cryptographictechnique storage devices 308 storing non-PQC cryptographic techniquesand non-PQC cryptographic performance information related thereto, oneor more PQC callbacks 310, one or more PQC cryptographic techniquestorage devices 312 storing PQC cryptographic techniques and PQCcryptographic performance information related thereto, and data 314. Insome embodiments, the PQC system 302 may be configured to perform PQC inaccordance with some example embodiments described herein (e.g., asdescribed with reference to apparatus 200 shown in FIG. 2A).

In some embodiments, the client device 320 may comprise communicationscircuitry configured to communicate with the one or more PQC serverdevices 304 over one or more non-PQC communications channels 324. Theclient device 320 may comprise, for example, a PQC shim 322 configuredto communicate with the one or more PQC callbacks 310 over one or morePQC communications channels 326. In some embodiments, the client device320 may be configured to perform PQC in accordance with some exampleembodiments described herein (e.g., as described with reference toapparatus 280 shown in FIG. 2B, wherein apparatus 280 comprises the PQCshim circuitry 260, and the PQC shim circuitry 260 comprises the PQCcryptographic circuitry 252).

FIG. 3B illustrates an example PQC system architecture 360 configured toperform various operations in accordance with some example embodimentsdescribed herein. The example PQC system architecture 360 may comprise,for example, the PQC system 302, a client device 330, and one or morePoS devices 338A-338N.

In some embodiments, the client device 330 may comprise the PQC shim332, an HSM 336, and a PoS interface device 334 comprising aconcentrator, gateway, store controller, terminal manager, and upgradedPoS proxy. The PoS interface device 334 may be configured to communicatewith the PoS devices 338A-338N over one or more non-PQC communicationschannels. The PoS interface device 334 may be further configured tocommunicate with the one or more PQC server devices 304 over one or morenon-PQC communications channels 324. The PQC shim 322 configured tocommunicate with the one or more PQC callbacks 310 over one or more PQCcommunications channels 326. In some embodiments, the client device 330may be configured to perform PQC in accordance with some exampleembodiments described herein (e.g., as described with reference toapparatus 280 shown in FIG. 2B, wherein apparatus 280 comprises the PQCshim circuitry 260, and the PQC shim circuitry 260 comprises the PQCcryptographic circuitry 252).

FIG. 4A illustrates an example PQC system architecture 400 configured toperform various operations in accordance with some example embodimentsdescribed herein. The example PQC system architecture 400 may comprise,for example, the PQC system 402, a client device 430, and a PQC add-ondevice 432.

In some embodiments, the PQC system 402 may comprise, for example, oneor more data storage devices 406 comprising search and other functions,one or more PQC server devices 404, one or more non-PQC cryptographictechnique storage devices 408 storing non-PQC cryptographic techniquesand non-PQC cryptographic performance information related thereto, oneor more PQC callbacks 410, one or more PQC cryptographic techniquestorage devices 412 storing PQC cryptographic techniques and PQCcryptographic performance information related thereto, and data 414. Insome embodiments, the PQC system 402 may be configured to perform PQC inaccordance with some example embodiments described herein (e.g., asdescribed with reference to apparatus 200 shown in FIG. 2A).

The client device 430 may comprise communications circuitry configuredto communicate with the one or more PQC server devices 404 over one ormore non-PQC communications channels 424. The PQC add-on device 432 maybe communicatively coupled to the client device 430 and configured tocommunicate with the one or more PQC callbacks 410 over one or more PQCcommunications channels 426. In some embodiments, the client device 430may not be configured to perform PQC in accordance with some exampleembodiments described herein (e.g., as described with reference toapparatus 280 shown in FIG. 2B, wherein apparatus 280 includes neitherthe PQC cryptographic circuitry 252 nor the PQC shim circuitry 260). Insome embodiments, the PQC add-on device 432 may be configured to performPQC for the client device 430 (e.g., on behalf of the client device 430)in accordance with some example embodiments described herein (e.g., asdescribed with reference to apparatus 290 shown in FIG. 2C).

FIG. 4B illustrates an example PQC system architecture 460 configured toperform various operations in accordance with some example embodimentsdescribed herein. The example PQC system architecture 460 may comprise,for example, the PQC system 402, a client device 440, a PQC add-ondevice 442, and one or more PoS devices 448A-448N.

In some embodiments, the client device 440 may comprise an HSM 446 and aPoS interface device 444 comprising a concentrator, gateway, storecontroller, terminal manager, and upgraded PoS proxy. The PoS interfacedevice 444 may be configured to communicate with the PoS devices 448A-8Nover one or more non-PQC communications channels. The PoS interfacedevice 444 may be further configured to communicate with the one or morePQC server devices 404 over one or more non-PQC communications channels424. The PQC add-on device 442 may be communicatively coupled to theclient device 440 and configured to communicate with the one or more PQCcallbacks 410 over one or more PQC communications channels 426. In someembodiments, the client device 440 may not be configured to perform PQCin accordance with some example embodiments described herein (e.g., asdescribed with reference to apparatus 280 shown in FIG. 2B, whereinapparatus 280 includes neither the PQC cryptographic circuitry 252 northe PQC shim circuitry 260). In some embodiments, the PQC add-on device442 may be configured to perform PQC for the client device 440 (e.g., onbehalf of the client device 440) in accordance with some exampleembodiments described herein (e.g., as described with reference toapparatus 290 shown in FIG. 2C).

FIG. 5 illustrates an example PQC system architecture 500 configured toperform various operations in accordance with some example embodimentsdescribed herein. The example PQC system architecture 500 may comprise,for example, the PQC system 502 and a set of client devices comprising aclient device 520A and a second client device 520B.

In some embodiments, the PQC system 502 may comprise, for example, oneor more data storage devices 506 comprising search and other functions,one or more PQC server devices 504, one or more non-PQC cryptographictechnique storage devices 508 storing non-PQC cryptographic techniquesand non-PQC cryptographic performance information related thereto, oneor more PQC callbacks 510, one or more PQC cryptographic techniquestorage devices 512 storing PQC cryptographic techniques and PQCcryptographic performance information related thereto, and data 514. Insome embodiments, the PQC system 502 may be configured to perform PQC inaccordance with some example embodiments described herein (e.g., asdescribed with reference to apparatus 200 shown in FIG. 2A). The PQCsystem 502 may further comprise quantum communications circuitry 516 andone or more quantum cryptographic technique storage devices 518 storingquantum cryptographic techniques and quantum cryptographic performanceinformation related thereto.

In some embodiments, the first client device 520A and the second clientdevice 520B may be embodied by any of the client devices shown in FIG.3A, 3B, 4A, or 4B, such as client device 320; client device 330; clientdevice 430 and PQC add-on device 432; or client device 440 and PQCadd-on device 442.

Further to the client devices shown in FIG. 3A, 3B, 4A, or 4B, the firstclient device 520A may comprise quantum communications circuitry 522A,and the second client device 520B may comprise quantum communicationscircuitry 522B. In some embodiments, the first client device 520A may becommunicatively coupled to a PQC add-on device comprising the quantumcommunications circuitry 522A, and the second client device 520B may becommunicatively coupled to a PQC add-on device comprising the quantumcommunications circuitry 522B.

In some embodiments, the client device 520A and the client device 520Bmay comprise communications circuitry configured to communicate with theone or more PQC server devices 504 over one or more non-PQCcommunications channels 524A and 524B, respectively, and to communicatewith each other over one or more non-PQC communications channels 534. Insome embodiments, the client device 520A and the client device 520B maycomprise communications circuitry configured to communicate with the oneor more PQC callbacks 510 over one or more PQC communications channels526A and 526B, respectively, and to communicate with each other over oneor more PQC communications channels 536. In some embodiments, the clientdevice 520A and the client device 520B may comprise quantumcommunications circuitry 522A and 522B, respectively, configured tocommunicate with the quantum communications circuitry 516 over one ormore quantum communications channels 528A and 528B, respectively, and tocommunicate with each other over one or more quantum communicationschannels 538.

Having described specific components of example devices and circuitriesinvolved in various embodiments contemplated herein, example proceduresfor PQC are described below in connection with FIGS. 6-8.

Example Operations for PQC

FIGS. 6A and 6B illustrate example flowcharts 600 and 630 that containexample operations for transmitting and receiving a portion of anelectronic communication over a PQC communications channel in accordancewith some example embodiments described herein. The operationsillustrated in FIGS. 6A and 6B may, for example, be performed by one ormore components described with reference to PQC system 102 shown in FIG.1; by a server device 110, a client device 112, a database server device114, or a remote server device 116 in communication with PQC system 102;by apparatus 200 shown in FIG. 2A; by apparatus 280 shown in FIG. 2B; byone or more components described with reference to PQC system 302 shownin FIGS. 3A and 3B; by a client device 320 (including, but not limitedto PQC shim 322), client device 330 (including, but not limited to PQCshim 332), or PoS device 338 in communication with PQC system 302; byone or more components described with reference to PQC system 502 shownin FIG. 5; by a client device 520 in communication with PQC system 502;or by any combination thereof.

In some embodiments, the various operations described in connection withFIGS. 6A and 6B may be performed by the apparatus 200 by or through theuse of one or more of processing circuitry 202, processing circuitry202, memory 204, input-output circuitry 206, PQC callback circuitry 207,communications circuitry 208, classical communications circuitry 210,quantum communications circuitry 212, data attribute generationcircuitry 214, data envelope generation circuitry 216, data structuregeneration circuitry 218, data monitoring circuitry 220, data accessmonitoring circuitry 222, data zone monitoring circuitry 224, policyattribute generation circuitry 226, risk profile generation circuitry228, vulnerability scan circuitry 230, vulnerability score generationcircuitry 232, compliance score generation circuitry 234, cryptographicperformance circuitry 236, non-PQC cryptographic performance circuitry238, PQC cryptographic performance circuitry 240, cryptographicattribute generation circuitry 242, non-PQC cryptographic attributegeneration circuitry 244, PQC cryptographic attribute generationcircuitry 246, cryptographic circuitry 248, non-PQC cryptographiccircuitry 250, PQC cryptographic circuitry 252, machine learningcircuitry 254, data storage circuitry 256, UI circuitry 258, PQC shimcircuitry 260, gateway circuitry 264, concentrator circuitry 266, storecontroller circuitry 268, terminal manager circuitry 270, PoS softwareupgrade circuitry 272, HSM circuitry 274, any other suitable circuitry,and any combination thereof.

Referring to FIG. 6A, as shown by operation 602, the apparatus 200includes means, such as classical communications circuitry 210 or thelike, for transmitting a first portion of an electronic communication toa client device (e.g., apparatus 280; client device 320; client device330; client device 520) over a non-PQC communications channel. In someembodiments, the first portion of the electronic communication maycomprise overhead data (e.g., protocol overhead, header, metadata). Insome embodiments, the first portion of the electronic communication maycomprise a session identifier. In some embodiments, the apparatus 200may transmit the first portion of an electronic communication to theclient device over the non-PQC communications channel as described inmore detail with reference to FIGS. 1-5.

As shown by operation 604, the apparatus 200 includes means, such as PQCcallback circuitry 207 or the like, for transmitting a second portion ofthe electronic communication to the client device (e.g., via PQC shim322; PQC shim 332) over a PQC communications channel. In someembodiments, the second portion of the electronic communication maycomprise payload data. In some embodiments, the second portion of theelectronic communication may comprise the session identifier. In someembodiments, the PQC communications channel may be a PQC back channel,such as a PQC out-of-band communications channel. In some embodiments,the apparatus 200 may transmit the second portion of the electroniccommunication to the client device over the PQC communications channelas described in more detail with reference to FIGS. 1-5.

Referring to FIG. 6B, as shown by operation 606, the apparatus 280includes means, such as classical communications circuitry 210 or thelike, for receiving a first portion of an electronic communication froma server device (e.g., apparatus 200; PQC server device 304; PQC serverdevice 504) over a non-PQC communications channel. In some embodiments,the first portion of the electronic communication may comprise overheaddata (e.g., protocol overhead, header, metadata). In some embodiments,the apparatus 280 may receive the first portion of the electroniccommunication from the server device over the non-PQC communicationschannel as described in more detail with reference to FIGS. 1-5.

As shown by operation 608, the apparatus 280 includes means, such as PQCcryptographic circuitry 252, PQC shim circuitry 260, or the like, forreceiving a second portion of the electronic communication from theserver device (e.g., via PQC callback 310; PQC callback 510) over a PQCcommunications channel. In some embodiments, the second portion of theelectronic communication may comprise payload data. In some embodiments,the PQC communications channel may be a PQC back channel, such as a PQCout-of-band communications channel. In some embodiments, the apparatus280 may receive the second portion of the electronic communication fromthe sever device over the PQC communications channel as described inmore detail with reference to FIGS. 1-5.

As shown by operation 610, the apparatus 280 includes means, such ascryptographic circuitry 248 or the like, for generating the electroniccommunication based on the first portion and the second portion of theelectronic communication. In some embodiments, wherein the first portionof the electronic communication comprises a session identifier, andwherein the second portion of the electronic communication comprises thesession identifier, the apparatus 280 may be configured to use thesession identifier to generate the electronic communication by combiningthe first portion of the electronic communication received over thenon-PQC communications channel and the second portion of the electroniccommunication received over the PQC communications channel. In someembodiments, the apparatus 280 may generate the electronic communicationas described in more detail with reference to FIGS. 1-5.

In some embodiments, operations 602, 604, 606, 608, and 610 may notnecessarily occur in the order depicted in FIGS. 6A and 6B, and in somecases one or more of the operations depicted in FIGS. 6A and 6B mayoccur substantially simultaneously, or additional steps may be involvedbefore, after, or between any of the operations shown in FIGS. 6A and6B.

FIGS. 7A, 7B, and 7C illustrate example flowcharts 700, 720, and 730that contain example operations for transmitting and receiving a portionof an electronic communication over a PQC communications channel using aPQC add-on device (e.g., apparatus 290 shown in FIG. 2C; PQC add-ondevice 432 shown in FIG. 4A; PQC add-on device 442 shown in FIG. 4B) inaccordance with some example embodiments described herein. Theoperations illustrated in FIGS. 7A, 7B, and 7C may, for example, beperformed by one or more components described with reference to PQCsystem 102 shown in FIG. 1; by a server device 110, a client device 112,a database server device 114, or a remote server device 116 incommunication with PQC system 102; by apparatus 200 shown in FIG. 2A; byapparatus 280 shown in FIG. 2B (e.g., wherein the apparatus 280 does notinclude the PQC cryptographic circuitry 252 or the PQC shim circuitry260); by apparatus 290 shown in FIG. 2C; by one or more componentsdescribed with reference to PQC system 402 shown in FIGS. 4A and 4B; bya client device 430, PQC add-on device 432, client device 440, PQCadd-on device 442, or PoS device 448 in communication with PQC system402; by one or more components described with reference to PQC system502 shown in FIG. 5; by a client device 520 in communication with PQCsystem 502; or by any combination thereof.

In some embodiments, the various operations described in connection withFIGS. 7A, 7B, and 7C may be performed by the apparatus 200 by or throughthe use of one or more of processing circuitry 202, processing circuitry202, memory 204, input-output circuitry 206, PQC callback circuitry 207,communications circuitry 208, classical communications circuitry 210,quantum communications circuitry 212, data attribute generationcircuitry 214, data envelope generation circuitry 216, data structuregeneration circuitry 218, data monitoring circuitry 220, data accessmonitoring circuitry 222, data zone monitoring circuitry 224, policyattribute generation circuitry 226, risk profile generation circuitry228, vulnerability scan circuitry 230, vulnerability score generationcircuitry 232, compliance score generation circuitry 234, cryptographicperformance circuitry 236, non-PQC cryptographic performance circuitry238, PQC cryptographic performance circuitry 240, cryptographicattribute generation circuitry 242, non-PQC cryptographic attributegeneration circuitry 244, PQC cryptographic attribute generationcircuitry 246, cryptographic circuitry 248, non-PQC cryptographiccircuitry 250, PQC cryptographic circuitry 252, machine learningcircuitry 254, data storage circuitry 256, UI circuitry 258, PQC shimcircuitry 260, gateway circuitry 264, concentrator circuitry 266, storecontroller circuitry 268, terminal manager circuitry 270, PoS softwareupgrade circuitry 272, HSM circuitry 274, any other suitable circuitry,and any combination thereof.

Referring to FIG. 7A, as shown by operation 702, the apparatus 200includes means, such as classical communications circuitry 210 or thelike, for transmitting a first portion of an electronic communication toa client device (e.g., apparatus 280; client device 430; client device440; client device 520) over a non-PQC communications channel. In someembodiments, the first portion of the electronic communication maycomprise overhead data (e.g., protocol overhead, header, metadata). Insome embodiments, the apparatus 200 may transmit the first portion of anelectronic communication to the client device over the non-PQCcommunications channel as described in more detail with reference toFIGS. 1-5.

As shown by operation 704, the apparatus 200 includes means, such as PQCcallback circuitry 207 or the like, for transmitting a second portion ofthe electronic communication to a PQC add-on device (e.g., apparatus290; PQC add-on device 432; PQC add-on device 442) over a PQCcommunications channel. In some embodiments, the PQC add-on device maybe communicatively coupled to a client device (e.g., apparatus 280;client device 430; client device 440; client device 520). In someembodiments, the second portion of the electronic communication maycomprise payload data. In some embodiments, the PQC communicationschannel may be a PQC back channel, such as a PQC out-of-bandcommunications channel. In some embodiments, the apparatus 200 maytransmit the second portion of the electronic communication to the PQCadd-on device over the PQC communications channel as described in moredetail with reference to FIGS. 1-5.

Referring to FIG. 7B, as shown by operation 706, the apparatus 290includes means, such as PQC cryptographic circuitry 252 or the like, forreceiving a second portion of the electronic communication from a serverdevice (e.g., apparatus 200; PQC server device 404 via PQC callback 410;PQC server device 504 via PQC callback 510) over a PQC communicationschannel. In some embodiments, the second portion of the electroniccommunication may comprise payload data. In some embodiments, the PQCcommunications channel may be a PQC back channel, such as a PQCout-of-band communications channel. In some embodiments, the apparatus290 may receive the second portion of the electronic communication fromthe sever device over the PQC communications channel as described inmore detail with reference to FIGS. 1-5.

As shown by operation 708, the apparatus 290 includes means, such as PQCcryptographic circuitry 252 or the like, for transmitting the secondportion of the electronic communication to a client device (e.g.,apparatus 280; client device 430; client device 440; client device 520).In some embodiments, the apparatus 290 may transmit the second portionof the electronic communication to the client device as described inmore detail with reference to FIGS. 1-5.

Referring to FIG. 7C, as shown by operation 710, the apparatus 280includes means, such as classical communications circuitry 210 or thelike, for receiving a first portion of an electronic communication froma server device (e.g., apparatus 200; PQC server device 404; PQC serverdevice 504) over a non-PQC communications channel. In some embodiments,the first portion of the electronic communication may comprise overheaddata (e.g., protocol overhead, header, metadata). In some embodiments,the apparatus 280 may receive the first portion of the electroniccommunication from the server device over the non-PQC communicationschannel as described in more detail with reference to FIGS. 1-5.

As shown by operation 712, the apparatus 280 includes means, such asclassical communications circuitry 210 or the like, for receiving asecond portion of the electronic communication from a PQC add-on device(e.g., apparatus 290; PQC add-on device 432; PQC add-on device 442). Insome embodiments, the second portion of the electronic communication maycomprise payload data. In some embodiments, the apparatus 280 mayreceive the second portion of the electronic communication from the PQCadd-on device as described in more detail with reference to FIGS. 1-5.

As shown by operation 714, the apparatus 280 includes means, such ascryptographic circuitry 248 or the like, for generating the electroniccommunication based on the first portion and the second portion of theelectronic communication. In some embodiments, the apparatus 280 maygenerate the electronic communication as described in more detail withreference to FIGS. 1-5.

In some embodiments, operations 702, 704, 706, 708, 710, 712, and 714may not necessarily occur in the order depicted in FIGS. 7A, 7B, and 7C,and in some cases one or more of the operations depicted in FIGS. 7A,7B, and 7C may occur substantially simultaneously, or additional stepsmay be involved before, after, or between any of the operations shown inFIGS. 7A, 7B, and 7C.

FIGS. 8A and 8B illustrate example flowcharts 800 and 830 that containexample operations for authenticating a session over a quantumcommunications channel and subsequently transmitting and receiving aportion of an electronic communication over a PQC communications channelin accordance with some example embodiments described herein. Theoperations illustrated in FIGS. 8A and 8B may, for example, be performedby one or more components described with reference to PQC system 102shown in FIG. 1; by a server device 110, a client device 112, a databaseserver device 114, or a remote server device 116 in communication withPQC system 102; by apparatus 200 shown in FIG. 2A; by apparatus 280shown in FIG. 2B; by apparatus 290 shown in FIG. 2C; by one or morecomponents described with reference to PQC system 502 shown in FIG. 5;by a client device 520 in communication with PQC system 502; or by anycombination thereof.

In some embodiments, the various operations described in connection withFIGS. 8A and 8B may be performed by the apparatus 200 by or through theuse of one or more of processing circuitry 202, processing circuitry202, memory 204, input-output circuitry 206, PQC callback circuitry 207,communications circuitry 208, classical communications circuitry 210,quantum communications circuitry 212, data attribute generationcircuitry 214, data envelope generation circuitry 216, data structuregeneration circuitry 218, data monitoring circuitry 220, data accessmonitoring circuitry 222, data zone monitoring circuitry 224, policyattribute generation circuitry 226, risk profile generation circuitry228, vulnerability scan circuitry 230, vulnerability score generationcircuitry 232, compliance score generation circuitry 234, cryptographicperformance circuitry 236, non-PQC cryptographic performance circuitry238, PQC cryptographic performance circuitry 240, cryptographicattribute generation circuitry 242, non-PQC cryptographic attributegeneration circuitry 244, PQC cryptographic attribute generationcircuitry 246, cryptographic circuitry 248, non-PQC cryptographiccircuitry 250, PQC cryptographic circuitry 252, machine learningcircuitry 254, data storage circuitry 256, UI circuitry 258, PQC shimcircuitry 260, gateway circuitry 264, concentrator circuitry 266, storecontroller circuitry 268, terminal manager circuitry 270, PoS softwareupgrade circuitry 272, HSM circuitry 274, any other suitable circuitry,and any combination thereof.

Referring to FIG. 8A, as shown by operation 802, the apparatus 200includes means, such as classical communications circuitry 210 or thelike, for transmitting a first portion of an electronic communication toa client device (e.g., apparatus 280; client device 520) over a non-PQCcommunications channel. In some embodiments, the first portion of theelectronic communication may comprise overhead data (e.g., protocoloverhead, header, metadata). In some embodiments, the apparatus 200 maytransmit the first portion of an electronic communication to the clientdevice over the non-PQC communications channel as described in moredetail with reference to FIGS. 1-5.

As shown by operation 804, the apparatus 200 includes means, such asquantum communications circuitry 212 or the like, for transmitting aquantum cryptographic key to the client device over a quantumcommunications channel. In some embodiments, the quantum cryptographickey may be a quantum key distribution (QKD) cryptographic key. In someembodiments, the quantum communications channel may comprise a quantumline, such as a polarization maintaining optical line. In someembodiments, the apparatus 200 may transmit the quantum cryptographickey to the client device over the quantum communications channel asdescribed in more detail with reference to FIGS. 1-5.

As shown by operation 806, the apparatus 200 includes means, such ascryptographic circuitry 248 or the like, for authenticating a sessionwith the client device over the non-PQC communications channel based onthe quantum cryptographic key transmitted to the client device over thequantum communications channel. In some embodiments, the apparatus 200may authenticate the session by performing a cryptographic handshakewith the client device over the non-PQC communications channel using thequantum cryptographic key. In some embodiments, the apparatus 200 mayauthenticate the session with the client device as described in moredetail with reference to FIGS. 1-5.

As shown by operation 808, the apparatus 200 includes means, such as PQCcallback circuitry 207 or the like, for transmitting a second portion ofthe electronic communication to the client device over a PQCcommunications channel. In some embodiments, the second portion of theelectronic communication may comprise payload data. In some embodiments,the PQC communications channel is a PQC back channel, such as a PQCout-of-band communications channel. In some embodiments, the apparatus200 may transmit the second portion of the electronic communication tothe client device over the PQC communications channel in response toauthentication of the session with the client device. In someembodiments, the apparatus 200 may transmit the second portion of theelectronic communication to the client device over the PQCcommunications channel as described in more detail with reference toFIGS. 1-5.

Referring to FIG. 8B, as shown by operation 810, the apparatus 280 or290 includes means, such as classical communications circuitry 210 orthe like, for receiving a first portion of an electronic communicationfrom a server device (e.g., apparatus 200; PQC server device 504) over anon-PQC communications channel. In some embodiments, the first portionof the electronic communication may comprise overhead data (e.g.,protocol overhead, header, metadata). In some embodiments, the apparatus280 or 290 may receive the first portion of the electronic communicationfrom the server device over the non-PQC communications channel asdescribed in more detail with reference to FIGS. 1-5.

As shown by operation 812, the apparatus 280 or 290 includes means, suchas quantum communications circuitry 212 or the like, for receiving aquantum cryptographic key from the server device over a quantumcommunications channel. In some embodiments, the quantum cryptographickey may be a QKD cryptographic key. In some embodiments, the quantumcommunications channel may comprise a quantum line, such as apolarization maintaining optical line. In some embodiments, theapparatus 280 or 290 may receive the quantum cryptographic key from theserver device over the quantum communications channel as described inmore detail with reference to FIGS. 1-5.

As shown by operation 814, the apparatus 280 or 290 includes means, suchas cryptographic circuitry 248 or the like, for authenticating a sessionwith the server device over the non-PQC communications channel based onthe quantum cryptographic key received from the server device over thequantum communications channel. In some embodiments, the apparatus 280or 290 may authenticate the session by performing a cryptographichandshake with the server device over the non-PQC communications channelusing the quantum cryptographic key. In some embodiments, the apparatus280 or 290 may authenticate the session with the server device asdescribed in more detail with reference to FIGS. 1-5.

As shown by operation 816, the apparatus 280 or 290 includes means, suchas PQC shim circuitry 260, PQC cryptographic circuitry 252, or the like,for receiving a second portion of the electronic communication from theserver device over a PQC communications channel. In some embodiments,the second portion of the electronic communication may comprise payloaddata. In some embodiments, the PQC communications channel may be a PQCback channel, such as a PQC out-of-band communications channel. In someembodiments, the apparatus 280 or 290 may receive the second portion ofthe electronic communication from the sever device over the PQCcommunications channel in response to authentication of the session withthe server device. In some embodiments, the apparatus 280 or 290 mayreceive the second portion of the electronic communication from thesever device over the PQC communications channel as described in moredetail with reference to FIGS. 1-5.

As shown by operation 818, the apparatus 280 or 290 includes means, suchas cryptographic circuitry 248 or the like, for generating theelectronic communication based on the first portion and the secondportion of the electronic communication. In some embodiments, theapparatus 280 or 290 may generate the electronic communication asdescribed in more detail with reference to FIGS. 1-5.

In some embodiments, operations 802, 804, 806, 808, 810, 812, 814, 816,and 818 may not necessarily occur in the order depicted in FIGS. 8A and8B, and in some cases one or more of the operations depicted in FIGS. 8Aand 8B may occur substantially simultaneously, or additional steps maybe involved before, after, or between any of the operations shown inFIGS. 8A and 8B.

As noted above, methods, apparatuses, systems, and computer programproducts are described herein that provide for improved PQC formigrating classical information systems to quantum-resistant informationsystems using one or more of the PQC cryptographic techniques describedherein. By doing so, data owners and hosting services are able to avoidthe traditional problems surrounding migrating classical informationsystems to quantum-resistant information systems. For instance, throughperformance of the above operations, data owners and hosting servicescan use the PQC system described herein to identify PQC cryptographictechniques for reducing the attack surface of their cryptographicoperations. In another instance, through performance of the aboveoperations, data owners and hosting services can use the QC detectionsystem described herein to detect realized QC threats and, in response,identify PQC cryptographic techniques for reducing the attack surface oftheir cryptographic operations. Further, example embodiments describedherein provide for migration of large volumes of data toquantum-resistant information systems that utilize PQC cryptographictechniques in a faster, cheaper, and less computing resource and dataintensive manner. Accordingly, example embodiments described hereinfacilitate and streamline these migration processes so that data ownersand hosting services may more quickly and easily migrate and maintaintheir data in a quantum-resistant PQC system before quantum computingcapabilities are realized. Moreover, in some embodiments, exampleembodiments described herein facilitate the upgrading of complex, highvolume data storage systems to use quantum-resistant PQC cryptographictechniques in a faster, cheaper, and less data and resource intensivemanner.

FIGS. 6-8 thus illustrate flowcharts describing the operation of varioussystems (e.g., PQC system 102 described with reference to FIG. 1; PQCsystem 302 described with reference to FIGS. 3A and 3B; PQC system 402described with reference to FIGS. 4A and 4B; PQC system 502 describedwith reference to FIG. 5), apparatuses (e.g., apparatus 200 describedwith reference to FIG. 2A; apparatus 280 described with reference toFIG. 2B; apparatus 290 described with reference to FIG. 2C), methods(e.g., flowcharts 600 and 630 described with reference to FIGS. 6A and6B; flowcharts 700, 720, and 730 described with reference to FIGS. 7A,7B, and 7C; flowcharts 800 and 830 described with reference to FIGS. 8Aand 8B), and computer program products according to example embodimentscontemplated herein. It will be understood that each operation of theflowcharts, and combinations of operations in the flowcharts, may beimplemented by various means, such as hardware, firmware, processor,circuitry, and/or other devices associated with execution of softwareincluding one or more computer program instructions. For example, one ormore of the procedures described above may be performed by execution ofcomputer program instructions. In this regard, the computer programinstructions that, when executed, cause performance of the proceduresdescribed above may be stored by a memory (e.g., memory 204) of anapparatus (e.g., apparatus 200) and executed by a processor (e.g.,processing circuitry 202) of the apparatus. As will be appreciated, anysuch computer program instructions may be loaded onto a computer orother programmable apparatus (e.g., hardware) to produce a machine, suchthat the resulting computer or other programmable apparatus implementsthe functions specified in the flowchart operations. These computerprogram instructions may also be stored in a computer-readable memorythat may direct a computer or other programmable apparatus to functionin a particular manner, such that the instructions stored in thecomputer-readable memory produce an article of manufacture, theexecution of which implements the functions specified in the flowchartoperations. The computer program instructions may also be loaded onto acomputer or other programmable apparatus to cause a series of operationsto be performed on the computer or other programmable apparatus toproduce a computer-implemented process such that the instructionsexecuted on the computer or other programmable apparatus provideoperations for implementing the functions specified in the flowchartoperations.

The flowchart operations described with reference to FIGS. 6-8 supportcombinations of means for performing the specified functions andcombinations of operations for performing the specified functions. Itwill be understood that one or more operations of the flowcharts, andcombinations of operations in the flowcharts, may be implemented byspecial purpose hardware-based computer systems which perform thespecified functions, or combinations of special purpose hardware andcomputer instructions.

Conclusion

While various embodiments in accordance with the principles disclosedherein have been shown and described above, modifications thereof may bemade by one skilled in the art without departing from the teachings ofthe disclosure. The embodiments described herein are representative onlyand are not intended to be limiting. Many variations, combinations, andmodifications are possible and are within the scope of the disclosure.Alternative embodiments that result from combining, integrating, and/oromitting features of the embodiment(s) are also within the scope of thedisclosure. Accordingly, the scope of protection is not limited by thedescription set out above, but is defined by the claims which follow,that scope including all equivalents of the subject matter of theclaims. Each and every claim is incorporated as further disclosure intothe specification and the claims are embodiment(s) of the presentdisclosure. Furthermore, any advantages and features described above mayrelate to specific embodiments but shall not limit the application ofsuch issued claims to processes and structures accomplishing any or allof the above advantages or having any or all of the above features.

In addition, the section headings used herein are provided forconsistency with the suggestions under 37 C.F.R. § 1.77 or to otherwiseprovide organizational cues. These headings shall not limit orcharacterize the disclosure set out in any claims that may issue fromthis disclosure. For instance, a description of a technology in the“Background” is not to be construed as an admission that certaintechnology is prior art to any disclosure in this disclosure. Neither isthe “Summary” to be considered as a limiting characterization of thedisclosure set forth in issued claims. Furthermore, any reference inthis disclosure to “disclosure” or “embodiment” in the singular shouldnot be used to argue that there is only a single point of novelty inthis disclosure. Multiple embodiments of the present disclosure may beset forth according to the limitations of the multiple claims issuingfrom this disclosure, and such claims accordingly define the disclosure,and their equivalents, that are protected thereby. In all instances, thescope of the claims shall be considered on their own merits in light ofthis disclosure but should not be constrained by the headings set forthherein.

Also, techniques, systems, subsystems, and methods described andillustrated in the various embodiments as discrete or separate may becombined or integrated with other systems, modules, techniques, ormethods without departing from the scope of the present disclosure.Other devices or components shown or discussed as coupled to, or incommunication with, each other may be indirectly coupled through someintermediate device or component, whether electrically, mechanically, orotherwise. Other examples of changes, substitutions, and alterations areascertainable by one skilled in the art and could be made withoutdeparting from the scope disclosed herein.

Many modifications and other embodiments of the disclosure set forthherein will come to mind to one skilled in the art to which theseembodiments pertain having the benefit of teachings presented in theforegoing descriptions and the associated figures. Although the figuresonly show certain components of the apparatus and systems describedherein, it is understood that various other components may be used inconjunction with the PQC system. Therefore, it is to be understood thatthe disclosure is not to be limited to the specific embodimentsdisclosed and that modifications and other embodiments are intended tobe included within the scope of the appended claims. For example, thevarious elements or components may be combined, rearranged, orintegrated in another system or certain features may be omitted or notimplemented. Moreover, the steps in any method described above may notnecessarily occur in the order depicted in the accompanying figures, andin some cases one or more of the steps depicted may occur substantiallysimultaneously, or additional steps may be involved. Although specificterms are employed herein, they are used in a generic and descriptivesense only and not for purposes of limitation.

What is claimed is:
 1. A system for post-quantum cryptography (PQC), thesystem comprising: classical communications circuitry configured totransmit a first portion of an electronic communication to a clientdevice over a non-PQC communications channel, wherein the client deviceis a non-PQC device; and PQC callback circuitry configured to transmit asecond portion of the electronic communication to a PQC add-on deviceover a PQC communications channel, wherein the PQC add-on device iscommunicatively coupled to the client device.
 2. The system of claim 1,wherein the PQC add-on device comprises a PQC peripheral devicecommunicatively coupled to the client device.
 3. The system of claim 1,wherein the PQC add-on device comprises a PQC application specificintegrated circuit (ASIC) installed within a housing of the clientdevice.
 4. The system of claim 1, wherein the PQC communications channelis a PQC back channel.
 5. The system of claim 4, wherein the PQC backchannel is a PQC out-of-band communications channel.
 6. The system ofclaim 1, wherein the first portion of the electronic communicationcomprises overhead data, and wherein the second portion of theelectronic communication comprises payload data.
 7. The system of claim6, wherein the electronic communication is a Society for WorldwideInterbank Financial Telecommunication (SWIFT) message, wherein theoverhead data comprises SWIFT message overhead data, and wherein thepayload data comprises SWIFT message payload data.
 8. The system ofclaim 1, wherein the first portion of the electronic communicationcomprises a cryptographic data attribute indicative of a symmetriccryptographic technique, and wherein the second portion of theelectronic communication comprises a symmetric cryptographic key.
 9. Thesystem of claim 8, wherein the symmetric cryptographic key is anAdvanced Encryption Standard (AES) symmetric cryptographic key.
 10. Thesystem of claim 8, further comprising cryptographic circuitry configuredto: authenticate a session with the client device over the non-PQCcommunications channel based on the symmetric cryptographic keytransmitted to the PQC add-on device over the PQC communicationschannel.
 11. The system of claim 1, wherein the first portion of theelectronic communication comprises a PQC indicator data structure thatindicates that the second portion of the electronic communication is tobe transmitted over the PQC communications channel.
 12. The system ofclaim 11, wherein the PQC indicator data structure comprises a link tothe second portion of the electronic communication.
 13. The system ofclaim 11, wherein the first portion of the electronic communicationcomprises a Transport Layer Security (TLS) extension comprising the PQCindicator data structure.
 14. The system of claim 11, wherein the firstportion of the electronic communication comprises an InternationalOrganization for Standardization (ISO) 8583 extension comprising the PQCindicator data structure.
 15. The system of claim 11, wherein the PQCindicator data structure is a PQC flag value.
 16. The system of claim11, wherein the PQC indicator data structure comprises a link to a PQCelectronic agreement.
 17. The system of claim 11, wherein the firstportion of the electronic communication comprises a PQC request datastructure, and wherein: the classical communications circuitry isconfigured to in response to transmission of the PQC request datastructure, receive a PQC acknowledgement data structure from the clientdevice over the non-PQC communications channel; and the PQC callbackcircuitry is configured to in response to receipt of the PQCacknowledgement data structure, transmit the second portion of theelectronic communication to the PQC add-on device over the PQCcommunications channel.
 18. The system of claim 1, wherein the firstportion of the electronic communication comprises a session identifier,and wherein the second portion of the electronic communication comprisesthe session identifier.
 19. A method for post-quantum cryptography(PQC), the method comprising: transmitting, by classical communicationscircuitry, a first portion of an electronic communication to a clientdevice over a non-PQC communications channel, wherein the client deviceis a non-PQC device; and transmitting, by PQC callback circuitry, asecond portion of the electronic communication to a PQC add-on deviceover a PQC communications channel, wherein the PQC add-on device iscommunicatively coupled to the client device.
 20. A computer programproduct for post-quantum cryptography (PQC), the computer programproduct comprising at least one non-transitory computer-readable storagemedium storing program instructions that, when executed, cause a systemto: transmit a first portion of an electronic communication to a clientdevice over a non-PQC communications channel, wherein the client deviceis a non-PQC device; and transmit a second portion of the electroniccommunication to a PQC add-on device over a PQC communications channel,wherein the PQC add-on device is communicatively coupled to the clientdevice.